Executions
An execution is a single run of a test case, suite, or regression, with status, timings, screenshots, and the outcome.
An execution is one run of a test case, test suite, or whole regression. It records the overall pass/fail status, when it ran and how long it took, the screenshots, and a written outcome explaining the result.
Executions start in two ways. Click Run on a single case, a suite, or an entire regression, or let a schedule fire a regression for you on a recurring cadence.
Reading a result
- Status: pass, fail, or another terminal state at a glance.
- Timing: who (or what) triggered it, when it started, and how long it took.
- Screenshots: what the browser showed during the run.
- Outcome: on a failure, a message explaining what went wrong; on a pass, an optional success note. For an Advanced case, any failed assertions are listed with the reason each one didn't hold.
A suite or regression run also shows a result summary and a table of its child runs, so you can drill into the specific case that failed.
Because steps are intent-based, a failing execution usually means the behavior changed. The agent re-resolves selectors on every run, so drift alone won't fail a test.