Forum Discussion

cmd125's avatar
cmd125
Occasional Contributor
2 years ago

WaitNamedChild not working

It seems as thought the WaitNamedChild method isn't working and doesn't find the element on screen. Instead it just waits until the set timeout time runs out. For example I use when I go to a certain...
  • cmd125's avatar
    cmd125
    2 years ago

    Please disregard. Not sure why but when I changed it to wait for a different element it worked. Thanks anyways.

  • cmd125's avatar
    cmd125
    2 years ago

    I think I figured it out. If an element has two different xpaths set in the namemappings but pointed to different elements, it doesn't work. I had added two different xpaths due to the differences between qa and dev so that my tests would work on both until qa was updated, but when qa got updated this occurred. I'm pretty sure that is what happened here and I hope this helps anyone else that runs into this problem. 

     

cmd125's avatar
cmd125
Occasional Contributor
2 years ago

I was on 15.52.2.7 x64 but updated to latest 15.54.3.7 x64 and it still occurs. Here's a function that I have that it's occurring with:

def test_function():
    if NameMapping.Sys.browser.Reservation.reservationButton.Exists == True:
          NameMapping.Sys.browser.Reservation.reservationButton.Click()
    NameMapping.Sys.browser.Reservation.WaitNamedChild("commentsTab", 12000)
    aqUtils.Delay(1000)