Coverage data requires the
@testdino/playwright reporter with coverage.enabled: true. See the Code Coverage guide for setup.Coverage Trends
A time-series chart plots coverage metrics (statements, branches, functions, lines) across the selected period. Each data point represents one test run. For sharded runs, the data point reflects the merged coverage across all shards. Use this chart to:- Spot sudden drops that match a specific commit or PR
- Confirm that adding new tests raised coverage
- Track progress toward a team coverage target
Coverage by Branch
Compare average statement coverage across branches. If a branch has lower coverage thanmain, tests are missing for the code changes on that branch.
Coverage Diff
The diff view compares coverage between two branches or time periods. It surfaces files where coverage changed, sorted by the largest regressions first.| Column | Description |
|---|---|
| File | Source file path |
| Base | Coverage percentage on the base branch |
| Compare | Coverage percentage on the compared branch |
| Change | Difference in coverage (positive or negative) |
- Validate that a feature branch maintains or improves coverage before merging
- Identify files that lost coverage after a refactor
- Compare coverage across environments or time periods
Filters
Narrow the data by time period, environment, or branch.| Filter | What it does |
|---|---|
| Time Period | Show coverage data within a date range |
| Environment | Scope to a specific environment (production, staging, etc.) |
| Branch | Focus on one or more branches |