Reading a run

The run page

Every run has its own page, reached from Runs in the sidebar, from a journey's Runs tab, or from the link in a CI job or an email. It shows:

• The verdict: passed, failed or error, how long it took, who or what started it.
• Each scenario as a section, headed by its name, with every check as a sentence that held or did not. A check that did not hold says why. A button above the list narrows it to the scenarios that failed.
• The video, with each check marked at the moment it was judged. Click a check to jump to that moment.
• Where it stopped, if it did not reach the end, naming the screen and the reason.

A run on a phone in our device lab gets its video a minute or two after it ends. Until then the page says the recording is being prepared.

The PDF report

Download report gives a PDF anyone can read without an account: a run, a whole platform's latest results, or a whole project's. It names every journey and scenario, including ones that have not run yet, so "all checks passed" never quietly means "half of it was never checked".

Since when

A journey's page and the dashboard show its last 14 runs as a strip of marks, oldest to newest. A one-off blip, a flaky check that comes and goes, and a break that has been red since Tuesday each look different, and the dashboard says it in words: "Checkout has been failing for 8 days".

The dashboard

The dashboard leads with what is true now: how many journeys are passing as of their latest run. Below it:

• What did not hold: every failing check in the words it was written in
• Since when: each journey's recent runs
• What the green does not cover: journeys with no checks, journeys that have never run, and schedules that came due and did not produce a run

In words

A journey's In words tab reads it as Given, When and Then, generated from what you recorded: the steps that lead to each scenario, the steps within it, and its checks. It is a readable summary for people who will never open the recorder.

For pipelines

Every run is also available as JUnit XML, the results file every CI system reads, with each check as a test case named by its sentence. See Running from CI.

How long reports are kept

Plan	Videos and screenshots kept
Pay as you go	90 days
Monthly credits	1 year

The run itself, its results and its PDF are kept for as long as the journey exists. Only the video and screenshots age out.