A Test Run Report shows the result of one execution of a Test Case: its status, each step with its result and screenshots, and where the test ran. You open it from the Test Runs list.
Open a Test Run Report
Open Test Runs in the left-hand navigation of your Project.
Find the Test Run that you want to review. Filter the list if needed.
Click the Test Run. The Test Run Report opens with the detailed results.
Review the report. It shows:
the Persona and the Environment of the run
the status of the run (Success, Failed, Cancelled, Not runnable). A Not runnable run did not start, because a value that the test needs has no value in the Environment
the date and the duration, for a finished run
the steps, with their results and screenshots
the browser, the location and the resolution of the run
Replay the test run
Below the browser view, the replay player plays the run again, step by step. You can pause and resume, skip and go back a step, and change the playback speed.
Self-healed steps
When the page changes under a test, Thunders can find the element again, and the step still passes. The report shows where this happened:
A self-healed step opens on its own when you open the report. During a live run, a self-healed step stays open when it finishes. A step that you close stays closed.
The action that healed carries a marker:
Self-healed: the cached selector no longer pointed at the element. Thunders found the element again, and the step passed.
Waited longer: the element was not ready in time. Thunders waited past the default time, and the step passed.
Click Self-healed to open the Target self-healed panel. Under Path, it shows the path to the element in the Recorded run and in This run, with the part that changed marked. Under Visual check, it shows a screenshot of the element in each run, when one is available. Click View the run it was recorded on to open the earlier run in a new tab.
In the list of Test Runs of a Test Case, a run with self-healed steps carries the self-healed icon, with the number of steps when there is more than one.
Errors visible on the page
A click can succeed while the page shows an error message, for example "Incorrect password". After a click or an Enter key press, Thunders checks the text that the action adds to the page. When it finds an error message, the step gets a warning sub-step, Error visible on the page, with the message that Thunders found. The step stays passed.
The check is on by default. To turn it off for the runs that use the QA Persona, open Personas in the Project, open the QA Persona, and turn off Detect errors visible on the page. A run that uses another Persona always runs the check.
Related articles on this topic that you might find helpful