The Coverage tab shows how much of your application code ran during a test run. It displays four overall metrics and a file-by-file breakdown so you can find exactly which parts of your code are untested.
This tab only appears when the @testdino/playwright reporter has coverage.enabled: true and your application is instrumented with Istanbul. See the Code Coverage guide for full setup instructions. Coverage Badge
Runs with coverage data display a coverage badge on the Test Runs list. The badge shows the overall statement coverage percentage, giving an at-a-glance indicator without opening the run.
| Badge color | Statement coverage |
|---|
| Green | 80% and above |
| Yellow | 50% to 79% |
| Red | Below 50% |
Coverage Summary
Four tiles at the top of the tab show the overall coverage for the run:
| Metric | What it means |
|---|
| Statements | How many individual code statements ran during tests |
| Branches | How many if/else paths were taken (both the true and false side) |
| Functions | How many functions were called at least once |
| Lines | How many source lines ran during tests |
Coverage by File
A table showing coverage metrics for every source file in the report. Each row displays statements, branches, functions, and lines percentages. Sort by any column to find the files with the lowest coverage.
Two view modes are available using the toggle in the top-right corner of the table:
List View
A flat list of all source files with their coverage percentages. Each file shows its full path relative to the project root.
Tree View
Files grouped by directory structure. Expand or collapse folders to drill into specific areas of your codebase. Each folder row shows the aggregate coverage for all files inside it. Use Expand All and Collapse All to control the tree.
Coverage Diff
The diff view compares coverage between the current run and a baseline. It highlights files where coverage increased or decreased, making it easy to spot regressions introduced by a specific change.
| Column | Description |
|---|
| File | Source file path |
| Current | Coverage percentage in this run |
| Baseline | Coverage percentage from the comparison run |
| Change | Difference between current and baseline (positive or negative) |
Use the diff view during code review to confirm that new code includes adequate test coverage before merging.
