Interactive tool
The Traceability Matrix.
Coverage is not a feeling, it is a map. This links every requirement to the test cases that prove it, then shows you the two things that bite: a high-risk requirement with no test, and a test case that traces to nothing. Build the matrix, read the gaps, and copy a clean version for the team. Your work saves in your browser, and nothing you type leaves it.
The matrix
Tick a cell where a test case proves a requirement. Click a status or risk chip to change it.
Coverage gaps, fix these first
Orphan test cases, trace or remove them
Shareable matrix
Field guide
Reading a matrix like a lead
A matrix is not paperwork. It is the fastest way to see what you have not tested yet, and where you are spending effort nobody asked for.
What it is for
A traceability matrix maps every requirement to the test cases that prove it. It answers the question a lead, an auditor or a release manager will eventually ask: how do you know this was tested?
Forward and backward
Read it forward and every requirement should reach at least one test, so nothing ships untested. Read it backward and every test should reach a requirement, so you are not spending time on cases nobody asked for.
Risk first
Coverage is not a number to maximise blindly. An uncovered low-risk label is a note for later. An uncovered high-risk requirement is the thing you write a test for today, before anything else.
Coverage is not passing
A requirement with a test still fails if that test is red. The matrix tracks both: is there a case at all, and is that case actually passing. A green coverage number over failing tests is a false comfort.
Where the cases come from
Write the cases in the Test Case Builder so each one is accurate, atomic and traceable, then bring the ids here to prove they cover the requirements. When a case goes red, hand it to the Bug Report builder. That is the loop: design, trace, run, report.