Requirements and Test Traceability Reviewer

How to use Requirements and Test Traceability Reviewer

Bring three small QA source tables into a single traceability review. Exact requirement and test identities keep joins explicit, while every effective association preserves its source link record and supplied test status. Missing references, repeated pairs and unlinked items stay visible instead of inflating coverage. The result describes the submitted records, not whether a product actually meets its requirements.

1. Enter exact-header CSV tables for one to one hundred requirements, zero to one hundred tests and up to five hundred links.
2. Use exact supplied status pass, fail, blocked or not-run; IDs join without trimming or case folding.
3. Inspect complete requirement evidence, orphan tests, dangling/duplicate link records and the chosen separate artifact.

Good to know

• At most 100,000 characters per CSV field and 200,000 combined. Required headers are exactly id,requirement; id,title,status; and requirementId,testId. Requirement text at most 300 characters, test title 200 and nonblank single-line IDs 60. Requirements and tests each require distinct IDs and equal-width records.
• Test status is exactly pass, fail, blocked or not-run. Titles and IDs are not interpreted as expressions. For a requirement, any effective fail takes precedence, then blocked, then not-run; otherwise a nonempty set is reported-all-pass. No effective link is uncovered. All linked status witnesses remain visible.
• A missing requirement/test reference remains a dangling source record and contributes no coverage. Duplicate requirement/test pairs retain their first-record witness and do not add a second effective association. Tests with no effective requirement link are orphans, even when a dangling link mentions them.
• Source record numbers count data records, excluding headers. Exact strings are preserved without normalization or fuzzy matching. JSON retains all source records; CSV uses separate row kinds for evidence and issues and applies spreadsheet formula protection while the JSON report retains originals.
• Printable source lists every requirement and its complete effective evidence, then dangling/duplicate links and orphan tests. Native layout remains a later check. No tests, code, browser, account or external resource are executed. Authored pass labels and links do not prove sufficient testing, verified requirements, NASA compliance or release readiness.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.