<t>Hello, <br/>
<br/>
I have run into an issue where every time I test a new version of my company’s software, the test breaks. Each time the test breaks I have checked the new version with Spy and I have noticed that Spy generates a different Xpath for elements with the new version compared to the Xpath searched for by the test.<br/>
<br/>
This is an example of an Xpath from the new version compared to an Xpath within the test:<br/>
<br/>
Test Xpath: [language=]/form[@automationid='ParentForm'] //button[@accessiblename='Add Job'][/language]<br/>
New Version Xpath: [language=]/form//button[@accessiblename='Add Job'][/language]<br/>
<br/>
I have tried to use different attributes and operators to make the Xpath stronger, but I can’t seem to get any consistency. I would love some suggestions. <br/>
<br/>
Also, just to provide some context, I’m creating these tests on a Windows 10 machine with Ranorex Studio 10.7.1. The software I’m testing has a user interface created with DevExpress WinForms. I have also included a snapshot of the element.</t>
How do I make a more robust Ranorex Xpath?
How do I make a more robust Ranorex Xpath?
You do not have the required permissions to view the files attached to this post.
Re: How do I make a more robust Ranorex Xpath?
You can check the robustness setting referenced in this thread: robust-path-disabling-t20538.html
and also a few tips about weighting attributes in this section of the user guide: https://support.ranorex.com/help/latest ... roduction/
In general, automationId is rather tricky, so if you have other attributes to rely on and you can skip the form with // , that is preferable.
and also a few tips about weighting attributes in this section of the user guide: https://support.ranorex.com/help/latest ... roduction/
In general, automationId is rather tricky, so if you have other attributes to rely on and you can skip the form with // , that is preferable.
