TestOwlView and Filter Your Test Run History
Run History is the complete record of every test run in your project. Use it to follow runs in progress, investigate failures, and re-run tests.
Each run records what was executed, where it ran, which environment it used, and how it went.
Overview
Two summary cards sit at the top of the page:
- Total Runs — how many runs there are, split into how many ran on the cloud and how many locally.
- Pass Rate — how many test-case attempts passed out of all those that finished.
Below them is a searchable, filterable list of runs. You can:
- Search by name or run ID.
- Filter by Status, Runner (Cloud or Local), and Trigger (Scheduled or Manual).
- Filter by a date range.
- Sort by Run ID or Started At.
What each column shows
| Column | Meaning |
|---|---|
| Run ID | The run's identifier. Hover it to see what was run (the target name and, for a suite, how many tests it contains). |
| Runner | Cloud or Local. Local runs also show Headed (a visible browser window) or Headless. |
| Environment | The environment the run used. |
| URL | The application address the run tested. |
| Trigger | Manual for runs you started, or Scheduled for runs started by a schedule. Click a Scheduled badge to open that schedule. |
| Run Execution | The run's status. Hover for a plain-language summary, such as "3 passed, 1 failed out of 4 tests." |
| Duration | How long the run took. |
| Started At | When it started. |
Run statuses
| Status | Description |
|---|---|
| Queued | The run is waiting to start. No tests have run yet. |
| Running | The run is in progress. Hover to see how many tests have finished so far. |
| Completed | The run finished. Individual test cases may still have passed or failed — open the report to see. |
| Failed | The run could not be completed because of an execution or infrastructure error. |
| Stopped | The run was manually stopped before it finished. |
| Expired | The run's screenshots, videos, and logs were removed after your plan's retention period. The run stays in the list, but its detailed report is no longer available. |
Retention depends on your plan
Viewing a run
Click any row to open its Report, which includes:
- Test execution results
- Step-by-step details
- Screenshots and video
- Console and network logs
- Failure information
Stopping a run
While a run shows Queued or Running, you can click Stop on its row to cancel it. It moves to the Stopped status; tests that already finished keep their results, and any that hadn't started or were mid-execution are left incomplete.
Re-running
Tick one or more runs and click Re-run in the toolbar. The Run dialog opens with the previous selection, environment, and settings filled in so you can review or change them before starting. See Triggering a Run.
One run per environment