About this tool
A traceability matrix answers two audit questions: is every requirement tested, and does every test exist for a reason? Enter requirements and test cases (or paste them as CSV, with quoted values and line breaks handled per RFC 4180), list the requirement IDs each test covers, and the matrix is built as you type. Each cell shows the linked test’s status, each requirement shows how many of its tests passed, and the summary reports overall coverage. Requirements with no tests, tests that trace to nothing, links to requirement IDs that do not exist and duplicate IDs are flagged. IDs are matched case-insensitively. Export the matrix as CSV for a spreadsheet or Markdown for a wiki.
How to use it
- Add requirements with an ID and description, or import them from CSV.
- Add test cases with their linked requirement IDs (comma-separated) and status, or import them.
- Review the coverage summary and the flagged gaps, then fix links or add tests.
- Export the matrix as CSV or Markdown.
Requirement Traceability Matrix Generator FAQ
What CSV columns can I import?
For requirements: ID and Description (or Title/Summary). For test cases: ID, Title, a column whose header contains "Req", "Link", "Cover" or "Trace", and Status. Without a header row, columns are read in that order. Status values pass, fail and blocked are recognised; anything else becomes Not run.
What is the difference between coverage and verified coverage?
Coverage counts requirements with at least one linked test. Verified coverage counts requirements whose linked tests have all passed. A requirement can be covered but not verified if its tests failed or have not run.
What is an orphan test case?
A test that is not linked to any requirement in the matrix. It may test something undocumented, belong to a removed requirement, or simply be missing its link. Each one is worth a look.