Playwright Test Runs

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

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

Tab	What it shows
Summary	Failed, flaky, and skipped groups with detailed analysis
Specs	Results by spec file
Errors	Failures grouped by cause
Configuration	Source, CI, system, and Playwright config
AI Insights	Per-run failure classification

Search and filters

Control	Purpose
Search	Commit message or run number (for example, `#1493`)
Time Period	Last 7, 14, or 28 days, Last 3 or 6 months, or Custom
Status	Filter by run status or by test-case outcome, in 2 sections of one dropdown (see below)
Branch	One or more branches
Tags	Test Run tags (`tdpw --tags`, `TESTDINO_TAGS`, or config) or Test Case tags (Playwright `tag` metadata). By default, a run matches if it has any of the selected tags. Turn on Match exact tags only to show only runs whose tags are exactly the selected set, with no extras.

More filters holds the rest:

Control	Purpose
Author	One or more authors
Environment	Mapped environments
Re-runs	Only re-runs or Hide re-runs. Without it, the list shows both
Test Controls	Changed by Test Controls, Had quarantined failures, or Critical test passed only on retry
Duration	Under Sort: Low to High or High to Low

The Status dropdown has 2 sections, and you can select from either or both:

Section	Options	Matches
Run status	Passed, Failed, Interrupted, Incomplete	The run’s overall status, as its badge shows it. Incomplete also covers a finished test run where some test results never arrived, or where part of it stopped before its first test, for example when global setup threw.
Has tests that are	Passed, Failed, Flaky, Skipped, Interrupted, Incomplete	Runs that contain a test case with that outcome

Use the Has tests that are section 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. Runs distributed across machines at runtime show a SWARM label, per-machine tabs, and the count of machines that have reported. Active runs also show their run-level tags and what started the run. A sharded run shows the tags from all of its shards. Active test run with sharded execution showing shard tabs, worker status, and live progress bar

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

Column	Description
Test Run	Run ID, start time, and executor (CI or Local). CI label opens the job. A re-run adds Re-run of #N, linking to the original test run.
Commit	Message, short SHA, author, and what started the run. Links to the Git host.
Branch & Environment	Branch, mapped environment, and run-level tag chips (`+N` when truncated)
Test Results	Passed, Failed, Flaky, Skipped, Interrupted, and total

What started the run

The Commit column shows what started each test run. Hover the label for more detail.

Label	Meaning
`Manual`	Started manually
`Push`	Started by a push
`PR`	Started by a pull request
`Scheduled`	Started on a schedule
`Re-run #N`	A re-run of the job in GitHub Actions
`API`	Started through an API
`Webhook`	Started by a webhook
`CLI`	A local run
`Not available`	The CI provider didn’t say what started the run

On GitHub Actions, GitLab CI, Azure DevOps, and Buildkite, the label also shows who started the run. This needs @testdino/playwright 2.10.2 or later.
Re-runs started from TestDino show Re-run of #N in the Test Run column instead.

Run-level tags

Label an entire run with --tags on tdpw test. These are separate from test-case tags set via annotations.

npx tdpw test -t "$TESTDINO_TOKEN" --tags "regression,smoke"

error: unknown option '--tags'

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:

npx tdpw test -t "$TESTDINO_TOKEN" --tags "regression,smoke"

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.

Tag type	Set via	Scope
Run-level	`tdpw --tags`, `TESTDINO_TAGS`, or config	Entire test run
Test-case-level	Playwright `tag` metadata and annotations	Individual test cases

Run detail header

Element	Description
Commit message	Message and run number
Environment / Branch	Mapped environment badge and branch name
Commit SHA / Author	Short SHA (links to Git host) and committer
What started the run	Same label as the run list. See What started the run.
Timestamp / Duration	Start time and total run time
Tags	Run-level chips (same labels as `tdpw --tags`)
`RE-RUN OF #N` badge	On a re-run, next to the run number. Links to the original test run. Reads `RE-RUN` when the original is no longer available.
Re-run	Runs only this test run’s failed or flaky test cases, on the same commit or the latest code. Shown once the test run has finished with at least 1 failed or flaky test case. See Re-run failed Playwright tests.
Debug with AI	Hands the test run to your AI assistant. See Debug with AI.
Print / Export	In the `...` menu beside Debug with AI. Builds a shareable PDF of the run. See Print and export a test run report.
Post PR comment	In the `...` menu beside Debug with AI.

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.

Column	Shows
Shard	Number, status, and Slowest tag when applicable
Duration	Shard runtime
Breakdown	Pass / fail / flaky / skipped mix
Test results	Totals per outcome

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.

Column	Shows
Split	Number, status, and duration bar
Duration	Split runtime
Breakdown	Pass / fail / flaky / skipped mix
Test results	Totals per outcome

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. When a split or shard fails before its first test, for example in global setup, the test run is marked Incomplete and Summary opens with This run is incomplete, naming each part that stopped and its error. In the Splits section, that split shows Did not start, and its tests are not counted in the results.

Machines breakdown

Runs distributed across machines at runtime (tdpw swarm) carry a SWARM badge and show a Machines section on Summary. Learn how to set the machines up in Swarm mode.

Column	Shows
Machine	Machine ID reported by the CI job, and the machine’s status
Timeline	How long the machine ran. A grey tail shows how much shorter it ran than the longest machine (Unused capacity on hover)
Duration	Machine runtime
Test results	Totals per outcome

A headline above the table names what happened, for example Split across 4 machines. runner-3 finished 45s early. While the run is in progress it reads Running across 4 machines. and counts the machines that have reported, not the machines you asked for. On a finished run, an Imbalance badge compares the slowest machine with the fastest. When no machine could run a spec file, the test run finalizes as Incomplete and the panel lists those specs under No machine could run. Those test cases produced no result at all, so an incomplete test run is a coverage gap rather than a failure. Click machine rows to filter Detailed Analysis to those machines. Learn how to read the panel in Read the Machines panel.

Summary

Failures and flakiness by cause

Errors

Group failures by the error that caused them

Test Cases

Evidence and AI analysis per test

Getting Started

Connect Your Pipeline

Test Intelligence

Guides

AI-Native Testing

Organization & Access

Integrations

Test Management

Data Security & Privacy

Resources

Open a run

Search and filters

Active test runs

Run list columns

What started the run

Run-level tags

Run detail header

Re-runs

Shards breakdown

Splits breakdown

Machines breakdown

Summary

Errors

Test Cases

​Open a run

​Search and filters

​Active test runs

​Run list columns

​What started the run

​Run-level tags

​Run detail header

​Re-runs

​Shards breakdown

​Splits breakdown

​Machines breakdown

Summary

Errors

Test Cases

Open a run

Search and filters

Active test runs

Run list columns

What started the run

Run-level tags

Run detail header

Re-runs

Shards breakdown

Splits breakdown

Machines breakdown