This article provides solutions for common RanoreXPath challenges, such as addressing playback failures, and handling changes after a Ranorex Studio update.
RanoreXPath is no longer valid on playback
A common issue occurs when a RanoreXPath works in Ranorex Spy but fails during test execution.
Solutions:
-
Run Ranorex Studio in Maintenance Mode: Maintenance Mode allows you to identify points of failure during test execution so that you can fix errors without having to wait for the entire test to complete.
-
Update RanoreXPath settings slider: If paths are failing, increase Robustness. This allows your paths to become more resistant to UI changes.
- Re-track the elements: Sometimes simply re-tracking the elements fixes broken paths. This can happen if the previous paths aren’t dynamically created or if certain UI elements have changed in your application.
Different RxPaths upon updating Ranorex Studio
When you update Ranorex Studio, you may notice that the RanoreXPath generated for a UI element differs from the path created in an older version. Because of this, your tests may fail.
Frequently updating the paths and maintaining the test scripts is generally recommended. This ensures that you use the latest available technology for RxPath generation and helps you maintain your tests.
If you want to update to the latest Ranorex Studio version, you can do the following to support paths created in versions before Ranorex Studio 10.7.6:
- Go to Settings > Plugins > WPF (if your application is in .NET Framework) or WPF.Core (if your application is in .NET Core)
- Change the Legacy paths without ContentPresenter elements setting to True and click OK.
- Restart your Application Under Test (AUT)
- Run your tests
With this setting enabled, you should experience the same or similar paths as in the previous versions.
If the application’s structure changes, then the paths change as well. Always adjust the testing scripts to match any development changes in your AUT.