Skip to main content
Requirements Traceability MatrixSmart PR Test SelectionAI Gap Analysis

Every Requirement,
Every Test, Live.

The Requirements Traceability Matrix links your refined stories, Jira issues, and generation records to the test cases that cover them — showing live coverage, run state, and business risk in one view. Paste a GitHub PR URL to get the smallest risk-ranked test set for that change in seconds.

78%Requirements Covered
62%Covered & Passing
3High-Risk Uncovered
RequirementRiskCoverageLast Run
Authentication · 2 of 3 covered
User login with email and passwordRefined Story SR-4A2F · 2 ACB0CoveredPassing
Password reset via email linkJira QA-17B1Uncovered—
Dashboard · 1 of 2 covered
Display test execution summaryRecord REC-B31CB2CoveredFailing
4
Live KPI metrics
Requirements Covered %, Covered & Passing %, High-Risk Uncovered, Total Requirements — updated on every load
B0–B3
Business-risk tiers
Critical (B0), High (B1), Medium (B2), Low (B3) — derived from story priority and test-case risk metadata
PR
Smart test selection
Paste a GitHub PR URL — the matrix maps changed files to requirements and returns the smallest risk-ranked test set
2
Credits per AI gap analysis
One AI call produces a verdict (critical / warning / pass), top uncovered gaps, and recommended next actions
Requirement Sources

Three kinds of requirements, one unified matrix

The matrix pulls requirements from every place QAEverest already stores them — no separate import step needed.

SR-4A2F

Refined Story

Every Story Refinement you create becomes a requirement row. Its acceptance criteria appear in the detail drawer, and its priority field drives the B0–B3 risk tier assigned to the row.

Acceptance criteriaPriority → risk tierDomain · Module
REC-B31C

Generation Record

Records created when you generate test cases (UserRecord) are linked automatically. Each record carries its domain, module, story detail, and test-case type — no manual mapping required.

Domain · ModuleStory detailTest-case type
QA-17

Jira Issue

Requirements imported from Jira appear with their issue key as the external reference — displayed alongside the requirement label and used for cross-tool traceability. Any test artifact can be linked to a Jira issue.

Jira issue keyIssue summaryProject context
Test Cases
Individual test cases linked directly — each shows its last run status (Passing / Failing / Not run) and business risk in the matrix row.
Suites
Link an entire suite in one step — all member test cases are resolved automatically, and coverage reflects the suite's worst-case run state.
Non-invasive by designTrace links live in their own collection — no foreign keys are added to existing story, record, or test-case schemas. The feature can be toggled off with zero data migration.
Smart Test Selection

Paste a GitHub PR. Get the exact tests to run.

The Smart Selection tab fetches a GitHub PR's changed files, maps them to your requirement matrix, and returns the smallest risk-ranked test set that covers the change — ranked failing and unknown first. Unmapped files are flagged so you know exactly where your matrix has blind spots.

1
Paste PR URL
GitHub pull request link — any repo with a connected token
2
AI Maps Changes
Changed files are matched to requirements in your matrix via heuristic analysis
3
Ranked Test Set
Smallest set covering the PR's risk, ranked by severity — ready to run
github.com / myorg / app / pull / 241Analyze PR
⚠3 requirements touched · 1 coverage gap detected
myorg / app #241 · 7 changed files · 3 requirements touched
9tests to run
94%risk covered
~4mvs ~28m full
1gap found
⚠1 changed requirement has no tests
B1Password reset via email link Generate
Recommended tests (9)
B0User login with email and passwordPassing▶ Run
B1OAuth token refresh on expiryNot run▶ Run
B2Session timeout after inactivityNot run▶ Run
Tests to run
The smallest set of test cases whose requirements are touched by the PR's changed files, ranked by business risk
Risk coverage %
Percentage of the touched requirement risk that the recommended test set covers
Estimated time
Rough estimate in minutes for the selected set vs. the full project suite
Coverage gaps
Changed requirements with zero linked tests — with a one-click Generate shortcut to fill the gap immediately

Run tests directly from the suite

Each recommended test that belongs to a suite has a Run shortcut. Clicking it navigates straight to that suite's history page so you can initiate execution and review results without searching manually.

PR analysis history

The last 10 PR analyses are stored locally. One click reloads any previous result — useful for comparing how coverage changes across multiple PRs targeting 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.

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.

Your recommended test set will appear here.

Explore Now!

Book a DemoBecome a Partner