A test suite without traceability is a map without labels.

Link tests to requirements. Surface gaps. Import code coverage. Track impact. Know what you're testing and what you're missing.

Requirements Linking

Create requirements with external IDs (JIRA-123, or your own schema). Types: FUNCTIONAL, TECHNICAL, UX, PERFORMANCE, SECURITY. Status: ACTIVE, DRAFT, DEPRECATED.

Link test cases with COVERS, VERIFIES, or RELATES_TO. Coverage gap analysis surfaces every requirement that has no linked test cases.

You can't close a coverage gap you haven't named.

Requirements Coverage

REQ-101User login

FUNCTIONALcovered

REQ-102Password reset

FUNCTIONALcovered

REQ-103Session timeout

SECURITYuncovered

REQ-104Mobile responsive

UXuncovered

2 of 4 requirements covered (50%)

Code Coverage

Import from JaCoCo, Codecov, Coveralls, Istanbul, or GCOV. Line, branch, and function coverage percentages. Per-file breakdown in JSON. Trend over time — daily and weekly averages. Branch and commit SHA tracking.

Coverage tied to a specific commit, not just a date.

Code Coverage — main

src/api/auth.ts

92%85%100%

src/api/checkout.ts

78%65%80%

src/api/search.ts

88%82%95%

src/ui/checkout.tsx

45%30%50%

Line · Branch · Function

Test Impact Analysis

Given a test case: find the requirements it covers and the other test cases that relate to the same requirements.

Understand the blast radius of a failing test. Understand the coverage implications of deprecating one.

Impact — TC-42: Checkout

Related Requirements

REQ-101 (Checkout flow)

REQ-104 (Payment processing)

Related Test Cases

TC-41 (Add to cart)

TC-43 (Payment validation)

TC-44 (Order confirmation)

Know your coverage.

Link tests to requirements, import code coverage, and understand the impact of every test.

Start Free Trial