Skip to main content
The Test Runs page lists every Playwright test run in your project. Filter the list, open a run, and use the detail tabs for evidence and AI insights.

​
Open a run

  1. Filter by time, environment, branch, status, or tags
  2. Scan result counts and open a run that needs action
  3. Use the detail tabs:

​
Search and filters

The Status filter has 2 tabs, and you can select from either or both: Use the Test Case tab to find runs with a flaky or skipped test, which the run-level status does not surface on its own.

​
Active test runs

Runs still executing appear in Active Test Runs at the top, with a live progress bar and pass/fail/skip counts. Sharded runs show a SHARDED label and per-shard tabs. Runs assembled from separate CI jobs show a SPLITTED label, a progress bar segmented per split, and per-split tabs. Active test run with sharded execution showing shard tabs, worker status, and live progress bar

​
Run list columns

Test runs list showing run ID, commit info, branch, environment, and test results counts

​
Run-level tags

Label an entire run with --tags on tdpw test. These are separate from test-case tags set via annotations.
You passed --tags to npx playwright test. Playwright does not define that flag, so it exits before the test run starts.Use the TestDino wrapper:
To keep npx playwright test, set tags in the reporter options. TESTDINO_TAGS and testdino.config.ts are read by tdpw only. Learn how to set run labels in Run-level tags.

​
Run detail header

​
Re-runs

A test run that has been re-run shows a row under its header with its latest re-run: the run number colored by status, the test case counts, the total, and when it started. With more than 1 re-run, View all N opens a table of them with Run, Results, Total, and Started columns, newest first. The table holds the 20 most recent and says so when there are more. A re-run inside the original GitHub run is labeled with its GitHub attempt, such as Attempt 2. When its retried jobs report as separate test runs, each carries the same label with the job count, such as Attempt 2 · 3 jobs. A re-run is left out of run-level figures: test run count, pass rate, and average duration. Its test cases still count in test-level views, and it is billed like any test run. Learn how to start one in Re-run failed Playwright tests.

​
Shards breakdown

Sharded runs (--shard) show a Shards section on Summary. Pass the same --ci-run-id to every shard so TestDino merges them into one run. Setup: Node.js CLI → Sharded runs. After the run finishes, imbalance (for example 3.0×) compares slowest to fastest shard. A failure-concentration note appears when one shard holds most failures. Click shard rows to filter Detailed Analysis to those shards.

​
Splits breakdown

Runs assembled from separate CI jobs (--split) carry a SPLITTED badge and show a Splits section on Summary in place of Shards. Learn how to set the jobs up in Split mode. A split that used --shard expands to a per-shard table, and Split and Shard act as independent filters. If 2 splits reported the same test cases, the panel warns that per-split counts may be unreliable: split statuses stay accurate while totals become approximate.

Summary

Failures and flakiness by cause

Errors

Group failures by error message

Test Cases

Evidence and AI analysis per test
Last modified on October 6, 2026