Read a test run report

Every run produces a report — the step-by-step record of what happened, with screenshots and timings. This guide is about reading one and finding old ones. To share a report, see How to share a test run report.

Find a run

Open Reports from the top nav. The list has a toggle between two histories:

• Tests — single-test runs.
• Test Sets — batch runs (a test set or tag run).

Narrow the list with the status pills (All / Passed / Failed / Stopped), the search box, a date-range picker, and — on the Tests view — a tag filter. The list is paginated; older runs are a page back, not gone (until they age out — see retention).

“Passed” means completed

The status pill says Passed, but under the hood that status is completed. If you’re reading the API or filtering programmatically, that’s the value you’ll see.

Read a single-test report

The report header shows the test name (or Quick Run if it wasn’t a saved test), an overall pass/fail icon, the duration, and when it ran. Below that is the step list. Each step shows:

• A status icon — passed, failed, or skipped.
• The step description and how long it took.
• A screenshot toggle, plus a button to open it full-size in the lightbox.
• On a failure: the error message (expandable, with a Copy button) and a diagnosis callout that explains why the locator or assertion didn’t land.

A failed step stops the rest

When a step fails, the steps after it are marked skipped — the run can’t meaningfully continue once a step didn’t do what it said. So “1 failed, 4 skipped” usually means one real failure, not five.

The screenshot lightbox

Click any screenshot to open the lightbox. Arrow keys (←/→) move between steps, Esc closes it, and you can download the full-size image to drop into a ticket.

Read a batch (test-set) report

A test-set or tag run rolls up into a batch report with stat cards — Passed / Failed / Skipped / Total — across every test, plus the browsers it ran on and the execution target (Cloud or Local). Below the rollup is the per-test breakdown.

Each row shows the test, its status badge, the per-test result, duration, and any error. Click a row to drill into that single test’s full report — same step list and screenshots as above.

From a batch report you can also Rerun the whole set or Rerun Failed — see Run tests and rerun the failures.

How long reports stick around

Run history is kept per plan tier:

Plan	Retention
Free	14 days
Starter	90 days
Pro	180 days
Team	2 years
Enterprise	Unlimited

Old runs are pruned automatically by a nightly cleanup, and downgrading shrinks your window (the downgrade preview shows what you’d lose). The full story on what’s stored and for how long is in Data handling.

Related

• Share a test run report — links, emails, and exports
• Run tests and rerun the failures — rerun from a report
• Capture and update visual baselines — reviewing visual diffs in a report
• Test statuses — the Draft / Ready / Archived badge on each test