Hi,
i am recording a web test but i have a problem:
after some click on some buttons, i have to click on a button in a tabber in a workarea (seei the picture in the attachments):
I tryed to register the test with Chrome and Firefox but the problem is the same, the action is present in the rxrec list but the test blocks itself at the time of the click because Ranorex can't find the button.
i also tryed with Spy to track the button....
In the attachments, i also make a Ranorex Snapshot of the button.
How can i solve the problem or a walkaround to solve?
Thanks in advance
Christian
Ranorex: 9.3 latest version
OS: Windows 10
Can't detect a button in a tabber...
Can't detect a button in a tabber...
You do not have the required permissions to view the files attached to this post.
Re: Can't detect a button in a tabber...
Hi,
Please show us the full xpath for given element (as is stored in repository). I guess that the problem is either in "iframe" src attribute or "li" unique ID, whci appears to be highly volatile to changes?
In the snapshot, Li element shows unique ID "tab7". My guess is, that the Li element stored in your repo has different number?
Eventually, there is changing the string in iframe src attribute? So, here is an example of xpath, which should work, regardless of iframe or li ID dynamic changes...
Please show us the full xpath for given element (as is stored in repository). I guess that the problem is either in "iframe" src attribute or "li" unique ID, whci appears to be highly volatile to changes?
In the snapshot, Li element shows unique ID "tab7". My guess is, that the Li element stored in your repo has different number?

/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='main-iframe']//li[@id~'tab']/a[@innertext='Sicurezza']
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Can't detect a button in a tabber...
Hi, thanks for the response...odklizec wrote: ↑Tue Apr 28, 2020 8:58 amHi,
Please show us the full xpath for given element (as is stored in repository). I guess that the problem is either in "iframe" src attribute or "li" unique ID, whci appears to be highly volatile to changes?
In the snapshot, Li element shows unique ID "tab7". My guess is, that the Li element stored in your repo has different number?Eventually, there is changing the string in iframe src attribute? So, here is an example of xpath, which should work, regardless of iframe or li ID dynamic changes...
/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='main-iframe']//li[@id~'tab']/a[@innertext='Sicurezza']
I'm not sure if the xpath is the first or the second field:
So i post both:
Code: Select all
/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@src='http://127.0.0.1/www/enc_url?u=DclU9UjOcpolTIDdXzmBHHSwZLuwQDabIIwJ2WBZeYhZoKtkMMVuNh_sOmfuLo7EzSEr9jGLWVkyvFU=&isRunningInNewContainer=1&wapid_=workarea_2_1588061161018&client_width=1920&client_height=957&x_az_id__=0']//form[#'myform']/table//div/ul/li[2]/a[@innertext='Sicurezza']
/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@src='http://127.0.0.1/www/enc_url?u=DclU9UjOcpolTIDdXzmBHHSwZLuwQDabIIwJ2WBZeYhZoKtkMMVuNh_sOmfuLo7EzSEr9jGLWVkyvFU=&isRunningInNewContainer=1&wapid_=workarea_2_1587997266406&client_width=1920&client_height=957&x_az_id__=0']//form[#'myform']/table//ul/li[2]/a[@innertext='Sicurezza']
Christian
You do not have the required permissions to view the files attached to this post.
Re: Can't detect a button in a tabber...
Hi
The first xpath is the actual one, the second one is previously stored/used xpath. As you can see, both have differences in iframe src attribute. You should definitely replace src attribute with something else, for example the class attribute I suggested. Also, in your xpath, there are used index numbers, which often changes too. Simply use the xpath I suggested and it should work.
The first xpath is the actual one, the second one is previously stored/used xpath. As you can see, both have differences in iframe src attribute. You should definitely replace src attribute with something else, for example the class attribute I suggested. Also, in your xpath, there are used index numbers, which often changes too. Simply use the xpath I suggested and it should work.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Can't detect a button in a tabber...
Hi,odklizec wrote: ↑Tue Apr 28, 2020 9:33 amHi
The first xpath is the actual one, the second one is previously stored/used xpath. As you can see, both have differences in iframe src attribute. You should definitely replace src attribute with something else, for example the class attribute I suggested. Also, in your xpath, there are used index numbers, which often changes too. Simply use the xpath I suggested and it should work.
i tryed your xpath in two ways:
Code: Select all
/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='main-iframe']//li[@id~'tab']/a[@innertext='Sicurezza']
/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='appframe']//li[@id~'tab']/a[@innertext='Sicurezza']

Maybe i have to change other parameters in the xpath? Maybe the iframe class?
Christian
Re: Can't detect a button in a tabber...
Hi,
The first one (the one I suggested) definitely works with the snapshot you posted.
The first one (the one I suggested) definitely works with the snapshot you posted.
The other one is incorrect, because class attribute for given iframe is 'main-iframe'. The 'appframe' you used belongs to 'name' attribute, so the xpath should look like this:/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='main-iframe']//li[@id~'tab']/a[@innertext='Sicurezza']
If neither xpath works for you, then please add "Create Snapshot" action directly before the failing action and point it to entire DOM element. And then please post the entire report you get after failure. Thanks./dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@name='appframe']//li[@id~'tab']/a[@innertext='Sicurezza']
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Can't detect a button in a tabber...
Hi,odklizec wrote: ↑Tue Apr 28, 2020 11:09 amHi,
The first one (the one I suggested) definitely works with the snapshot you posted.The other one is incorrect, because class attribute for given iframe is 'main-iframe'. The 'appframe' you used belongs to 'name' attribute, so the xpath should look like this:/dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@class='main-iframe']//li[@id~'tab']/a[@innertext='Sicurezza']If neither xpath works for you, then please add "Create Snapshot" action directly before the failing action and point it to entire DOM element. And then please post the entire report you get after failure. Thanks./dom[@domain='127.0.0.1']//div[#'workAreasContainer']//iframe[@name='appframe']//li[@id~'tab']/a[@innertext='Sicurezza']
i build the long path in this way:
Code: Select all
/dom[@domain='127.0.0.1']//div[@id='content']//div[@id='content-column']/div[@id='workAreasContainer']/div[3]/div[2]/div[1]/iframe[@name='appframe']//form[@name='myform']//div[@class='tabberlive']//ul[@class='tabbernav']/li[@id='tab7']/a[@title='Sicurezza']
Re: Can't detect a button in a tabber...
Hi,
While this xpath might work right now, I would strongly recommend to remove all divs with indexes and replace @id='tab7' with @id~'tab'. Try this xpath instead...
While this xpath might work right now, I would strongly recommend to remove all divs with indexes and replace @id='tab7' with @id~'tab'. Try this xpath instead...
Anyway, the original xpath I posted should work too. But it may be a good idea to make the xpath a bit more precise./dom[@domain='127.0.0.1']//div[@id='content']//div[@id='content-column']/div[@id='workAreasContainer']//iframe[@name='appframe']//form[@name='myform']//div[@class='tabberlive']//ul[@class='tabbernav']/li[@id~'tab']/a[@title='Sicurezza']
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Can't detect a button in a tabber...
Hi,odklizec wrote: ↑Tue Apr 28, 2020 12:41 pmHi,
While this xpath might work right now, I would strongly recommend to remove all divs with indexes and replace @id='tab7' with @id~'tab'. Try this xpath instead...Anyway, the original xpath I posted should work too. But it may be a good idea to make the xpath a bit more precise./dom[@domain='127.0.0.1']//div[@id='content']//div[@id='content-column']/div[@id='workAreasContainer']//iframe[@name='appframe']//form[@name='myform']//div[@class='tabberlive']//ul[@class='tabbernav']/li[@id~'tab']/a[@title='Sicurezza']
that's strange, i tryed your last xpath but doesn't work:
I don't know why, i'm sorry, i use Ranorex Studio from 7 days....
With the my long xpath yes....
Christian
You do not have the required permissions to view the files attached to this post.
Re: Can't detect a button in a tabber...
Hi ducarpit!
Try to Track your button again and after this to delete extra parameters in XPath. Also check all / and // (maybe somewhere extra).
P.s.: did you change parameters of identification? Plugins?
Try to Track your button again and after this to delete extra parameters in XPath. Also check all / and // (maybe somewhere extra).
P.s.: did you change parameters of identification? Plugins?