Reading run results

Every run keeps enough evidence to answer "what happened?" without running it again.

The run page

Open any run from Runs, from a test's Run history, or from a Play All batch. You'll see:

• The result and timing: status, site, who started it and how, and how long it took (shown as Browser time).
• Steps: each step and check with its result and duration. A failed step is highlighted, with the error message in plain English.
• Evidence: screenshots taken at each step, the full replay video and the trace.

Screenshots and video

Screenshots show the page at each step, so you can scroll through the run like a flip book. The replay video shows the whole run in real time, which is useful for spotting animations, slow loads and pop-ups.

Passwords and other secrets are masked in both.

Traces

The trace is a Playwright trace file: a complete recording of the run with the page structure, network requests and console messages at every step. Download it and either:

• drop it onto trace.playwright.dev, which runs entirely in your browser and uploads nothing, or
• open it with Playwright's trace viewer on your computer.

Traces are the deepest level of detail. Most failures are clear from the screenshot alone.

Compare two runs

On a test page, press Compare last two above the run history to see two runs side by side, step by step. It's the fastest way to see what changed between the last green run and the first red one.

How long results are kept

Screenshots, traces and run videos are kept for the number of days set under Workspace settings → Run artifact retention. Screenshot baselines used by "Looks the same as before" checks are kept regardless. See Security and data.