Actions and the report
In this chapter, you’ll learn how actions executed during a test run are represented in the report.
In this chapter
Screencast
The screencast “Actions and the report” walks you through the information found in this chapter.
How actions are reported
By default, every action executed during a test run triggers a report message.
Actions reported during a test run
As you can see in the image above, one action means at least one report message, and sometimes more. In large test suites that have thousands of actions, the report can get cluttered very quickly. To prevent this, you can use ⇢ report levels to control which report messages make it into the report.
You can reduce the number of actions recorded in a Report at the Test Suite level by using the Filter Actions in the Report Properties.
In the Filter Actions drop-down select which Actions you want to be recorded in the test suite report. By default, all actions are selected.
Reference
Disabling reporting for actions is explained in:
>Ranorex Studio fundamentals >Actions >⇢ Manage actions
What actions look like in the report
Actions can be separated into four groups in terms of how they appear in the report:
- Failed or successful validations
- Separators
- User-defined log messages
- All other actions
Validations
Validation report messages always have two parts. The first part has the report level Info and is just a notification that a validation has been performed.
The second, more interesting part, tells you whether the validation succeeded or failed.
Successful validation
A successful validation has the report level Success and is printed in green by default.
Failed validation
A failed validation has the report level Failure, has a red background, and usually comes with two screenshots to make it easier to find out what went wrong.
Reference
To learn more about validations, refer to the chapters:
Ranorex Studio fundamentals > Actions > ⇢ Action properties and
Ranorex Studio fundamentals > ⇢ Test validation
Separators
Separators are useful for visually structuring actions in the actions table and the report.
A separator in the actions table with the header Validation action next.
In the report, the separator has the report level Info and its message displays the header defined in the actions table.
Further reading
For more information on separators, refer to
Ranorex Studio fundamentals > Ranorex Recorder > ⇢ Managing recording modules and
Ranorex Studio fundamentals > Actions > ⇢ Action properties
User-defined log messages
With the Log message action, you can pass a custom message with a custom report level to the report.
Log message in the actions table.
The same log message in the report.
Further reading
For more information on the Log message action, refer to
Ranorex Studio fundamentals > Actions > ⇢ Action properties
All other actions
All other actions have the report level Info and their message describes what they are doing. If such an action fails, a separate message with the report level Failure will be passed to the report, in the same way as described further above for validations.
The Mouse click action has the report level Info and its text describes that a left click was performed on the specified repository item at the specified screen coordinates.