Every Requirement,
Every Test, Live.
The Requirements Traceability Matrix (RTM) links your refined stories, Jira issues and generation records to the tests that cover them, with live run results, business risk and UAT status on every row. Export it to Excel or PDF for your release review, and paste a GitHub PR URL to get a risk-ranked test set for that change.
Three kinds of requirements, one unified matrix
The matrix pulls requirements from every place QAEverest already stores them, one row per story, with no separate import step.
SR-4A2FRefined Story
Every Story Refinement you create becomes a requirement row. Its acceptance criteria appear on the row's coverage report, and its priority sets the row's risk tier until a linked test carries a tier of its own.
REC-B31CGeneration Record
Every time you generate test cases, the record becomes a row, linked to the scenarios it produced. Build an automation suite from it, or import a repository, and the suite is linked too. No manual mapping required.
QA-17Jira Issue
Test cases you generate from a Jira issue keep its issue key, so the row shows the key as its reference and a reviewer can follow the Jira story straight to the tests that cover it.
From coverage to sign-off, in one view
Open a requirement, re-run its tests, check its UAT result and hand the whole matrix to your release review, all from Traceability.
Requirement Coverage Report
Click any row for a full-page report: coverage, linked tests, last run and business risk, then the acceptance criteria, the story, its trace lineage and its UAT cases. An uncovered row offers Generate tests for this, and the new scenarios are linked back to it.
Re-run from the matrix
Run on a linked test opens its suite and re-runs just that test when it has run before. Each row's result is read from its suites' recent runs, so it fails as soon as one linked test fails.
UAT status and filter
Filter rows by Accepted, Failing, Not run or No UAT cases, and choose whether a row reads each case's latest result or counts any failure in any cycle.
Excel and PDF export
The workbook carries Summary, Requirements, Linked tests and UAT cases sheets. The PDF is an A4 summary with the counts and every requirement shown, grouped by module.
Suggest Coverage (AI)
For uncovered rows, the AI finds the most similar covered requirement in the matrix and proposes its tests as coverage. Accept them all, or keep them as suggestions.
AI Gap Analysis
Top gaps and recommended actions in plain language. The verdict (pass, warning or critical) comes from fixed rules. Credits are charged only when the AI answers; if it can't, you get the rule-based analysis free.
Paste a GitHub PR. Get a risk-ranked set of tests to run.
The Smart Selection tab reads a pull request's changed files, matches them to the requirements in your matrix, and recommends tests highest business risk first until 95% of the touched risk is covered, always including every B0 test. Files it can't match are listed, so you can see where the matrix has blind spots.
The PR bot, pull request checks and CI steps are on the Pull Request & CI Testing page.
Run Selected
Tick the recommended tests and Run Selected starts one run per suite. Run on a single test opens its suite so you can start it there.
PR analysis history
Your last 10 PR analyses are kept in this browser and listed on the History tab. One click reloads a result, so you can compare PRs that touch the same module.
Unmapped file callout
Files the PR changed that couldn't be matched to any requirement are listed separately, making coverage blind spots explicit rather than silently ignored.
Find the duplicates and the gaps in what you already have
The Test Case Audit tab scans your test cases and suites with fixed rules, with no AI and no credits, and sorts what it finds into five lists. The last five audits stay on the History tab, each with its change since the one before.
- Duplicates. Exact copies, and cases with the same title but different steps, which are often an outdated copy. Compare them, keep the suggested one, or mark Not a duplicate.
- Not automated. Generated test cases with no automated test found for them.
- Data variants. Same steps, different test data. Not duplicates: each group could become one data-driven test case.
- Automation-only. Automated tests with no generated test case behind them.
- Category gaps. Categories selected at generation time that produced no test cases.
The matrix feeds your go/no-go
The Quality Command Center reads the matrix before a release. By default a critical requirement with no runnable test, or with a failing one, blocks the release, and one that hasn't run yet raises a warning. Each rule can be set to block, warn or off for the project. Every rule is on the Quality Command Center page.
- Critical requirement untestedBlock
- Critical requirement failingBlock
- Critical requirement not runWarn
- UAT sign-off pendingBlock
See It In Action
Paste a GitHub PR URL and preview the risk-ranked test set Smart Selection recommends — 4 tests covering 92% of the risk.