While competing in the exacting modern software market, many companies find integrating automated testing into their overall testing process beneficial. This guide will help you better understand the different types of automated test solutions and how developers...
Maintenance mode allows you to catch and resolve certain errors during test execution. You can then apply the fixes to your test suite from the report. This saves time because you don’t have to let the entire test run through to start diagnosing and fixing errors.
In this chapter
Activate maintenance mode
Under Build > Set configuration, ensure Debug is enabled. The option is usually enabled by default. It is not the same as the debug mode you enable from the menu bar.
In the test suite view, click the Maintenance mode switch to enable it.
Now when you run your test, it will be executed in maintenance mode. When you close the test suite view and reopen it, maintenance mode will be turned off again.
Tests cannot be run in maintenance mode on a Ranorex Agent.
Catch and resolve errors
When maintenance mode is active, it catches errors native to Ranorex Studio and pauses test execution upon doing so. Depending on the error type, different dialogs with different options will appear.
Some options are always available:
|Open report||Opens the report.|
|Continue with error||
Continues test execution according to the ⇢ error behavior set for the test container.
|Abort test run||Aborts the test run.|
Element not found
This dialog is displayed when a UI element couldn’t be found. It displays the related error message and the RanoreXPath for the associated repository item.
Click Edit and retry to open Ranorex Spy. You can then retrack the element or change its path manually. Once you apply the changes in Spy, Ranorex Studio will automatically try to run the failed action again with the updated path.
You can also click Retry to try again without changing anything. This is useful if you think the path is correct and the element couldn’t be found because the search timeout was too short or the AUT hadn’t reached the correct state yet.
This dialog is displayed when an expected validation value didn’t match the actual one. It displays the validation error message with the expected and actual values.
The drop-down menu contains the expected value (first option) and the actual value (second option). Select the actual value and then click Apply and retry to run the failed action again with this value.
Image validations cannot be resolved in maintenance mode. The generic dialog will be displayed for them.
This dialog appears for all Ranorex-Studio-native errors that are currently not resolvable in maintenance mode. Click Open Spy to inspect the affected element in Ranorex Spy. This can help you diagnose why the error occurred.
Apply your fixes
Once you’ve resolved the errors that appeared in maintenance mode and your test has executed successfully, you can apply the fixes to your test suite in the report.
In the report, maintenance mode events are indicated by a special icon:
Expand the report item to receive more information and find the maintenance mode event with the green check mark.
Hover over it and click the Apply… button to apply the fix to your test.
Fixes for variables and data bindings cannot be applied automatically. You will need to manually fix these in the respective test container or data source. This applies to both validation values and RanoreXPaths.