Why RTM Generator?
A traceability matrix is the artifact every reviewer asks for and nobody wants to maintain by hand - so it goes stale the week after it is written. This generator builds it from two pasted lists (requirements and tests, mapped as you type): coverage gaps, orphan tests, and broken references show up immediately, and the export is a table you can commit next to the code instead of a spreadsheet living in someone’s drive.
- Read gaps by priority: an uncovered High requirement is a release risk; an uncovered Low may be a decision you already made.
- Orphan tests are not automatically bad - each one is either an undocumented requirement or a test worth deleting. Decide per case.
- Re-export the matrix whenever the suite changes; it takes seconds, which is the whole point.
What is RTM Generator?
RTM Generator builds a requirements traceability matrix while you type: paste your requirements and your test cases, map each test to the requirements it covers, and the tool shows exactly which requirements have no tests, which tests are not mapped to anything, and what share of each priority tier is covered. A requirement with zero linked tests is flagged as a gap the moment it loses coverage, and a test referencing a requirement ID that does not exist surfaces as a broken reference instead of silently vanishing. Export the finished matrix as Markdown for a repo wiki or CSV for Excel, Google Sheets, or a test-management import - everything runs in your browser, with nothing uploaded.
Common Use Cases
Auditing Coverage Before a Release
Paste the requirement list and the test suite and see the gaps immediately: every requirement with zero tests is listed with its priority, before sign-off rather than after a customer finds it.
Producing a Traceability Artifact for Compliance
Regulated and enterprise projects ask for a requirements-to-tests mapping as a deliverable. Generate it in minutes and export CSV or Markdown instead of hand-maintaining a spreadsheet that goes stale.
Catching Orphan Tests
A test that maps to no requirement is either documenting something nobody wrote down or testing something nobody asked for. Both are worth knowing before the suite grows further.
Handing a Suite to the Next Tester
The matrix is the map: whoever picks the suite up next sees which requirements each test protects and where new tests are needed first.
How to Use This Tool
- Paste requirements, one per line - add a priority after a bar (High/Medium/Low or Must/Should/Could); IDs are generated automatically if you do not have them
- Paste test cases, one per line, mapping each with an arrow: Valid login succeeds -> REQ-101, REQ-102
- Read the summary: coverage percentage, per-priority breakdown, uncovered requirements, orphan tests, and broken references
- Copy the Markdown table or download CSV and keep it next to the tests it describes
Related Tools
Learn More
- ISTQB Glossary Official glossary of software testing terms, including traceability and coverage definitions.
- ISO/IEC/IEEE 29119-3:2021: Test Documentation The international standard for software test documentation templates, including the traceability between requirements and tests.
- FDA: General Principles of Software Validation FDA guidance describing how requirement traceability supports software validation in regulated industries.