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 error message
Configuration	Source, CI, system, and Playwright config
Coverage	Per-run code coverage
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, on 2 tabs (see below)
Duration	Sort low to high or high to low
Author	One or more authors
Environment	Mapped environments
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.

The Status filter has 2 tabs, and you can select from either or both:

Tab	Options	Matches
Test Run	Passed, Failed, Interrupted, Incomplete	The run’s overall status
Test Case	Passed, Failed, Flaky, Skipped, Interrupted, Incomplete	Runs that contain a test case with that outcome

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.

Run list columns

Column	Description
Test Run	Run ID, start time, and executor (CI or Local). CI label opens the job.
Commit	Message, short SHA, and author. 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

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 TESTDINO_TAGS, tags in testdino.config.ts, or tags in the reporter options. 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
Timestamp / Duration	Start time and total run time
Tags	Run-level chips (same labels as `tdpw --tags`)
Debug with AI	Hands the test run to your AI assistant. See Debug with AI.

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.

Summary

Failures and flakiness by cause

Errors

Group failures by error message

Test Cases

Evidence and AI analysis per test

Getting Started

Installation & Setup

AI & MCP

Guides

Project

Test Management

Organization

Integrations

Data Privacy

Resources

Open a run

Search and filters

Active test runs

Run list columns

Run-level tags

Run detail header

Shards breakdown

Splits breakdown

Summary

Errors

Test Cases

​Open a run

​Search and filters

​Active test runs

​Run list columns

​Run-level tags

​Run detail header

​Shards breakdown

​Splits breakdown

Summary

Errors

Test Cases

Open a run

Search and filters

Active test runs

Run list columns

Run-level tags

Run detail header

Shards breakdown

Splits breakdown