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
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.
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
- User-defined log messages
- All other actions
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.
A successful validation has the report level Success and is printed in green by default.
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.
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.
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.
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.