Test Coverage
2 min read
The Test Coverage report shows the percentage of requirements covered by tests, the percentage of tests automated, and how both break down by folder. Use it to find coverage gaps, track automation progress, and surface stale tests that have not run recently.
Recent window
Section titled “Recent window”A single filter controls the “executed recently” signal: choose Last 7 days, Last 14 days, Last 30 days, Last 60 days, or Last 90 days. This window determines which test cases count as having been executed recently.
Headline metrics
Section titled “Headline metrics”Three headline metrics summarize the project:
- Requirements covered: Coverage percentage, with the covered / total requirement counts.
- Tests automated: Automation percentage, with the automated / total test case counts.
- Tests executed (last Nd): The percentage of test cases executed within the selected recent window.
Tests automated counts the test cases whose automation field says they are automated. That field is maintained by hand, which is exactly why the panel below exists.
What CI actually ran
Section titled “What CI actually ran”Below the headline metrics sits a panel measured from build results over the recent window, rather than from the automation field. It reconciles what people said about the suite against what the pipelines actually did.
| Metric | Meaning |
|---|---|
| Run by a pipeline | The share of test cases that have build results |
| Stale automation | Marked automated, no build has run them |
| Not yet marked | A pipeline runs them, the field says otherwise |
Stale automation is the number worth watching. A test case marked automated that no build has touched is either automation that quietly broke, or automation that never existed — and either way it has been inflating your automation percentage.
Not yet marked is the cheerful opposite: work that is already automated but not recorded as such. Updating the field there costs nothing and makes the headline metric truthful.
The headline Tests automated percentage keeps its original meaning — the two are shown side by side on purpose, because the difference between them is the finding.
Coverage by requirement type
Section titled “Coverage by requirement type”A breakdown table shows, for each requirement type, the total requirements, how many are covered, how many are uncovered, and the resulting coverage.
Per-folder coverage
Section titled “Per-folder coverage”The per-folder table breaks coverage and automation down by folder, including each folder’s total tests, automation percentage, covered vs total requirements, coverage percentage, last executed date, and recent additions.
Uncovered requirements and stale tests
Section titled “Uncovered requirements and stale tests”- Uncovered requirements: A searchable list of the requirements that have no linked test case yet — the gaps to close first.
- Stale tests watchlist: Test cases that have not been executed within the recent window.
Exporting
Section titled “Exporting”Download the report as a PDF or as Excel (XLSX). The PDF dialog lets you choose sections — cover page, executive summary, coverage & automation KPIs, automation mix, coverage by requirement type, per-folder coverage, uncovered requirements, and the stale tests watchlist.