Feature · Insights · Traceability
Requirement to bug,
one thread.
The matrix assembles itself from requirement IDs — click a requirement and follow its whole chain.
Click a requirement — the chain assembles
REQ-004 has no cases — the gap shows up before the run, not in the release meeting.
In the product
How it actually works.
Tag cases with requirement IDs
Every test case carries a requirement ID field. Fill it as you write or approve — that is the entire setup.
The matrix assembles itself
Requirements group their cases, cases carry their last-run status, bugs attach to the chain. A coverage ring shows how much of the suite is linked.
Gaps surface early
Requirements with zero test cases get flagged before anything runs — the release meeting reads the matrix instead of discovering the hole live.
See these steps on screen
coming soonA guided video of this exact flow is being recorded — it will live right here.
Spec sheet