Coverage & Traceability Reports

Coverage & Traceability

Coverage reports help you answer a critical question: "Are all of our requirements being tested?" These five reports track the relationship between your requirements and test cases, ensuring nothing falls through the cracks. All coverage reports are Tier 1.

Requirement Coverage

Chart type: Donut | Tier: 1

Displays the percentage of requirements that are covered by at least one test case. The donut chart shows two segments: covered requirements and uncovered requirements, with the coverage percentage prominently displayed in the center.

Key insights: A coverage percentage below your team's threshold (e.g., 80%) signals that new test cases need to be written before the requirement can be considered fully validated. Track this metric over time using the Requirement Coverage Trend report.

When to use: At the start of each sprint or release to verify that new requirements have corresponding test cases. Also useful during test planning to identify gaps.

Test Case Coverage

Chart type: Donut | Tier: 1

The inverse of Requirement Coverage -- this report shows the percentage of test cases that are linked to at least one requirement. Test cases without requirement links may be orphaned or may need to be traced back to their originating requirement.

Key insights: A low percentage here suggests your test suite has grown organically without strict traceability. This can lead to wasted effort on tests that do not map to any business requirement.

When to use: During test suite audits and cleanup efforts. Pair with the Unlinked Test Cases table to find and fix orphaned tests.

Traceability Matrix

Chart type: Table | Tier: 1

Provides a full mapping between requirements and their linked test cases. Each row shows a requirement along with the test cases that validate it, including the latest execution status of each linked test case.

The Traceability Matrix is essential for regulated industries (healthcare, finance, aerospace) where you need documented proof that every requirement has been tested and verified. It also serves as a powerful audit artifact for ISO, SOC 2, and other compliance frameworks.

Key insights: Requirements with all linked tests passing are green. Requirements with any failing test are flagged. Requirements with no linked tests are highlighted as gaps.

When to use: Before release sign-off in regulated environments. Share with auditors or stakeholders to demonstrate complete traceability.

Uncovered Requirements

Chart type: Table | Tier: 1

Lists all requirements that are not linked to any test case. This is the action-oriented companion to the Requirement Coverage donut -- instead of showing a percentage, it gives you the exact list of requirements that need test cases.

When to use: Assign these uncovered requirements to testers during sprint planning so test cases are created before execution begins.

Unlinked Test Cases

Chart type: Table | Tier: 1

Lists all test cases that are not linked to any requirement. These are potential orphans -- tests that exist in your suite but do not trace back to a documented requirement.

When to use: During test suite cleanup. Review each unlinked test case and either link it to the appropriate requirement or consider archiving it if it is no longer relevant.