Prove Requirements Coverage

Review whether a feature’s requirements have current Test Cases. Identify missing or outdated coverage, then inspect execution results separately.

Start with Reqode

Coverage that starts from product behavior

Reqode evaluates Test Cases connected to Requirements and presents mutually exclusive coverage states across the effective Main Branch.

Currently covered

The Requirement has accounted Test Cases and none of those Test Cases reference an older Requirement revision.

Covered by outdated tests

At least one accounted Test Case was designed against a Requirement revision that is no longer current.

Uncovered

The Requirement has no accounted Test Case, making the gap visible before release review.

See coverage at the level where decisions happen

Start with the overall project indicator, compare coverage by subsystem, and navigate the Requirements folder and module tree to find specific gaps.

Because coverage follows Requirement revisions, the dashboard distinguishes having a test from having a test that still reflects the current product behavior.

Tests grouped by requirement, with outdated coverage and execution states across Test Runs.

TC-34: steps and expected results need review after the overlap requirement changes. — Tests grouped by requirement, with outdated coverage and execution states across Test Runs.

Turn the coverage matrix into action

Design missing tests

Send uncovered Requirements to AI Test Designer to prepare reviewable Test Cases and steps.

Review outdated tests

Inspect Requirement changes and update Test Cases whose saved Requirement revision is no longer current.

Run and refresh evidence

Assemble current Test Cases into Test Runs, record results, and combine coverage with execution evidence.

Requirements coverage

Answers whether specified product behavior has an associated, current Test Case. It helps product, QA, and delivery teams reason about validation completeness.

Not code coverage

Reqode does not claim that a Requirement relationship proves every source line or branch was executed. Code coverage and Requirement coverage answer different questions and work best together.

Coverage proves presence and currency—not automatic compliance

Reqode provides traceable evidence that Requirements are linked to current Test Cases and makes visible where that evidence is missing or stale. The project team still owns test quality, execution depth, and any regulatory interpretation.

See how code changes can make execution evidence need re-validation

Explore the workflow

Inspect missing and outdated coverage in FieldDesk, then choose the next action from concrete test evidence.

Start from requirement coverage

FieldDesk coverage is 59.17%. Compare test presence and currency before inspecting execution evidence in individual cases.

Make requirements coverage visible and actionable

Find missing and outdated QA evidence before it becomes a release surprise.