Requirements Traceability Matrix Generator

Runs in browser New Test Design

Paste your requirements and your test cases from Excel, Google Sheets or CSV — or open an .xlsx workbook with one sheet of each. The generator finds the ID, title, priority, link and status columns from their headers, joins the links recorded on either side, and builds the traceability matrix: which tests cover each requirement and the requirement's execution state. It reports requirements without tests, test cases that trace to no requirement, links to IDs that do not exist, duplicated IDs, links recorded on one side only, IDs that match only when case is ignored and unrecognised statuses, with linked coverage and execution coverage calculated from the data and broken down by priority. Exports the matrix as CSV, a requirement × test grid and a Markdown report. Everything stays in your browser.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

What is a requirements traceability matrix?

Traceability is the ability to follow the relationship between requirements and the test cases that verify them, in both directions. A requirements traceability matrix (RTM) records those links — usually with each test's latest result — so the team can see which requirements have no test, which tests trace to nothing, and how much of the agreed scope has passed. A link shows intent to cover a requirement, not that the test is adequate, so the tests themselves still need review.

Read the guide: Software Testing Life Cycle (STLC)

How to use Requirements Traceability Matrix Generator

  1. Prepare two tables with a header row: requirements (ID, title, optionally priority) and test cases (ID, title, the requirement IDs each covers, optionally status).
  2. Copy each table from your spreadsheet and paste it into its field — or choose an .xlsx workbook containing both sheets.
  3. Press Build matrix and check the note that lists the columns read.
  4. Read the coverage figures, then the lists: requirements without tests are gaps, tests without a requirement need a link or a reason, and mapping problems are data to correct.
  5. Download the matrix CSV or the Markdown report for the test summary or the release review.

Requirements Traceability Matrix Generator features

  • Paste requirements and test cases from Excel, Google Sheets or CSV, or open an .xlsx workbook with one sheet of each
  • Finds the ID, title, priority, link and status columns from their header names (in English, Arabic or Hindi), and says which columns it used
  • Joins links recorded on the test cases ("Requirement IDs"), on the requirements ("Test cases") or on both, and flags links recorded on one side only
  • Reports requirements without tests, tests without a requirement, links to IDs that do not exist, duplicated IDs, case-only ID mismatches and unrecognised statuses, with the row number
  • Calculates linked coverage and execution coverage from the data, per requirement state (passed, failed, blocked, partly passed, not run, not covered) and by priority
  • Exports the matrix and every list as CSV, a requirement × test grid for spreadsheets, and a Markdown report

Requirements Traceability Matrix Generator example

Sign-in and password-reset requirements

Input:

Requirements REQ-1…REQ-6 (High/Medium/Low); test cases TC-01…TC-07 with Requirement IDs and Status — TC-05 also links REQ-7, TC-06 has no requirement, TC-07 links "req-6" in lower case

Output:

Linked coverage 83.3% (5/6) · Execution coverage 33.3% (2/6 fully passed) · REQ-2 Failed (TC-03) · REQ-4 Not run · REQ-5 Not covered · REQ-6 Blocked · Orphan test: TC-06 · Mapping problems: TC-05 → REQ-7 does not exist; TC-07 "req-6" matched REQ-6 only when ignoring case · By priority: High 3/3 covered, Low 0/1

When to use Requirements Traceability Matrix Generator

  • Preparing the coverage section of a test summary report or a release go/no-go meeting
  • Finding requirements nobody wrote a test for before the sprint review
  • Cleaning up a test repository: tests that trace to removed requirements, duplicated IDs and typos in links
  • Giving auditors or a client a traceability matrix built from the team's own spreadsheets

Frequently asked questions about Requirements Traceability Matrix Generator

What is a requirements traceability matrix?

A table that links each requirement to the test cases that verify it (and often to their results and defects). It shows at a glance which requirements are untested, which tests trace to nothing, and how much of the agreed scope has passed — the questions asked before a release and in audits.

What format do my tables need?

A header row and one row per item. Requirements need an ID and a title (priority is optional). Test cases need an ID, a title, a column with the requirement IDs they cover, separated by commas, and optionally a status such as Passed, Failed, Blocked or Not run. Links may instead be listed on the requirements in a "Test cases" column, or on both sides.

How is coverage calculated?

Linked coverage is the share of requirements with at least one valid linked test. Execution coverage is the share of requirements whose linked tests all passed. Both are counted from your data only; a link to an ID that does not exist is reported, not counted.

Can I import an Excel file?

Yes. Choose an .xlsx workbook with one sheet of requirements and one of test cases; sheets whose names contain "req" and "test" are found automatically, otherwise the first two sheets are used. Copying the rows from Excel or Google Sheets into the two fields works as well.

Is my data uploaded?

No. Parsing and the matrix are computed in your browser and nothing is sent. Copying the results works without an account; downloading files asks you to sign in to a free account.

Technical notes

Pasted text is split on tabs when the first line contains one (a spreadsheet copy), otherwise read as CSV with the delimiter detected (comma, semicolon or pipe) and quoted fields supported. Link cells are split on commas, semicolons, pipes, the Arabic comma and new lines, or on spaces when every word looks like an ID.

IDs are matched ignoring upper and lower case and surrounding spaces, and every case-only match is reported so the source can be corrected. A duplicated ID keeps its first row; the links of the duplicates are merged into it and the duplicate is reported.

A requirement's state comes from its linked tests: Failed if any failed, else Blocked if any is blocked, Passed if all passed, Partly passed if some passed, otherwise Not run; with no valid link it is Not covered. Statuses are read in English, Arabic and Hindi; anything else is reported and counted as not run.

Limitations and methodology

Coverage here means traceability: a link says a test is meant to verify a requirement, not that the test is good enough to do so. Review the content of the tests as well.

Only explicit IDs create links; the tool does not infer links from titles or text. For suggestions from text, the AI Test Coverage Analyzer can help, and its results should be reviewed.

Workbooks are read without formulas being recalculated (the saved results are used), up to 5,000 rows and 30 columns per sheet.

Security and privacy

Requirements and test cases are parsed in your browser; nothing is uploaded or stored. Copying works without an account; downloading files asks you to sign in to a free account.

References

  • ISTQB GlossaryISTQBThe standard definitions of testing terms — test case, regression testing, severity, priority, boundary value analysis and the rest.
  • ISTQB Certified Tester Foundation Level (CTFL) v4.0ISTQB · 2023The foundation syllabus of software testing: test levels and types, test design techniques, test management and tools.