Requirement Traceability Matrix
2 min read
The Requirement Traceability Matrix maps every requirement to the test cases that cover it and the defects they caught. It is the report to reach for when you need to prove coverage, find requirements that are still untested, or spot the requirements that carry the most risk for a release.
Each row is a requirement. Expanding a row reveals its evidence: the linked test cases (with automation status) and the linked defects (with status).
Choosing a validation scope
Section titled “Choosing a validation scope”At the top of the report you pick a Validation scope (release or test run). This controls which test results are used to measure validation and risk:
- A whole release uses results across all of that release’s executions.
- A single execution — a release’s child run, or a standalone test run — measures validation against just that run.
The scope picker groups options under Releases and Test runs.
Headline metrics
Section titled “Headline metrics”The report summarizes the requirements in scope with coverage and validation percentages — how many requirements have at least one linked test, and how many have been validated — alongside the count of open defects.
Filtering the matrix
Section titled “Filtering the matrix”A search box (Search requirements, tests, defects…) and a Risk filter are always visible. Open the advanced filters to narrow further:
- Coverage: Covered vs uncovered requirements.
- Validation: Validated, not validated, or failed/blocked.
- Type: Requirement type.
- Status: Requirement workflow status.
- Folder: Requirements within a folder.
- Labels: Requirements carrying selected labels.
You can sort the matrix by Requirement, Coverage, Validation, or Risk.
Reading the columns
Section titled “Reading the columns”Each requirement row shows:
- Requirement: Code and title.
- Releases and Test runs: Where the requirement is exercised.
- Coverage: Whether and how many test cases are linked.
- Validation: The pass percentage across the validation records in scope.
- Risk: A computed risk level — High, Watch, or Healthy — based on coverage, failing or blocked tests, open critical/blocker defects, and how recently the requirement was last run.
Exporting
Section titled “Exporting”Use the export controls to download the matrix as a PDF or as Excel (XLSX). The PDF dialog (Configure PDF export) lets you include a cover page, an executive summary, coverage KPIs, a risk distribution, an automation summary, the coverage matrix table, and an optional per-requirement breakdown with each requirement’s linked test cases and defects.