Runs and the queue.
What happens between clicking Run and seeing a verdict.
Every run is queued and picked up by a runner pool within about a second; you may see a brief Queued badge before Running. Interactive runs (from the editor or a run dialog) get priority over batch fan-outs, and a slot is always reserved for them, so a big suite never blocks your debug run.
Runs are crash-safe: if a worker dies mid-run, the run is automatically requeued and re-executed; after repeated failures it lands as an honest error rather than hanging forever.
The Runs page lists everything with filters, per-row cancel (while queued or running) and delete. The run detail page shows a step-by-step timeline (failed steps expand automatically with the error and screenshot), plus tabs for Trace, Video, Console, and AI reasoning, and a JUnit XML export. A pass that needed a retry is labeled Passed (flaky).