Skip to main content
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.
WarningThis tab only appears when the @testdino/playwright streaming reporter (Experimental) 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.

​
Coverage Summary

Coverage summary showing statement, branch, function, and line coverage metrics Four tiles at the top of the tab show the overall coverage for the run:

​
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

Coverage list view showing per-file coverage percentages A flat list of all source files with their coverage percentages. Each file shows its full path relative to the project root.

​
Tree View

Coverage tree view showing files grouped by directory with aggregate coverage 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. The baseline defaults to the previous run on the same branch. For pull request runs, the baseline is the latest run on the target branch.
TipUse the diff view during code review to confirm that new code includes adequate test coverage before merging.

Code Coverage Guide

Set up instrumentation and coverage collection

Coverage Trend

Track coverage trends across runs

Summary

Group failures and flakiness by cause

Specs

Review results by spec file