Read a run
Steps, recordings, screenshots and traces, and what each result means.
Open Runs and choose a run. The page says how the run ended, then shows each test's recording beside its steps.
The run page Link to The run page
- The sentence at the top says how the run ended, when, how long it took and how it started. For a single test, it names the step where the test stopped.
- The recording plays the browser as the test used it. Click a step to jump to that moment.
- The steps list what the test did. Steps that check something are marked and stand out from the actions around them.
- The line under the recording shows the environment, the address and the browser. When GitHub started the run, it also shows the commit.
- A run of several tests lists them above the steps, failures first. Choose a test to see its recording.
A test's own page shows its newest runs as a row of squares. Choose one to see that run's recording and steps.
When a test fails Link to When a test fails
The step that failed opens in the list. When the test compared two values, it says what it expected and what the page showed. Under that is the line Playwright reported.
Press Show the screenshot to see the page as the test left it. Show the recording switches back.
If your app changed on purpose, open the run's menu, press Edit in chat and tell Re:agent what changed. If your app is broken, fix it and press Run again.
While it runs Link to While it runs
The test that is running shows Live view, the browser as it is now. Its recording appears when the test finishes. The page updates by itself.
What each result means Link to What each result means
| Result | What it means |
|---|---|
| Passed | The test took every step and every check passed. |
| Failed | A step or a check did not pass. The run shows which one. |
| Needs update | The test could not find an element it uses. The page changed where the test reads it. |
| Blocked | Rehearsal could not check the test. Its test account or a file was removed, or the browser could not reach your app. |
| Not ready | The test had not passed in a fresh browser when the run started, so it was not checked. |
| Did not run | The run ended before this test started, for example because someone stopped it. |
A run passes only when every test in it passed. It is Failed when a test failed or needs an update, Blocked when a test could not be checked, and Cancelled when someone stopped it.
Could not run means a problem on our side stopped the run. It counts towards nothing, so run it again when you are ready.
Recordings, screenshots and traces Link to Recordings, screenshots and traces
Each test in a run keeps a recording, screenshots and a Playwright trace. To get the trace, open the run's menu and press Download the trace. Open it with Playwright's trace viewer.
npx playwright show-trace <trace-file>A test that ran against an app on your computer keeps no trace. It still has its recording and screenshots.
When a file could not be saved, the run says so, such as The recording was not saved for this test.
Emails about runs Link to Emails about runs
When a run fails, is blocked or could not run, Rehearsal emails the members of the workspace. When a run passes after failing, they get an email saying so.
Next steps Link to Next steps
- Change a test with Edit in chat.
- Group tests into suites and run them together.