AgileTest
AgileTest
Breadcrumbs

Coverage Analysis

1. Overview

Coverage Analysis in AgileTest is the process of evaluating how well requirements are covered by tests. It is determined by the Coverage Status of a Requirement (shortly called Requirement Status) based on the test case statuses or test run item statuses.

There are 6 types of Requirement Status: NOK ; not run ; Unknown ; ok ; Uncovered ; covered . These statuses allow testers to quickly see which requirements have been fully tested, which are still in progress, and which may need additional testing.

CleanShot 2026-10-22 at 14.27.22@2x.png

For AgileTest to calculate the Requirement Status based on the scope of Test Cases or Test Scripts, you need to link test cases/test scripts to their corresponding requirements.

When you change the analysis scope & click Apply, AgileTest automatically recalculates the coverage status to reflect the selected scope.

Read more about:

Apply Test Case Scope To Calculate Requirement Status

Apply Test Script Scope to Calculate Requirement Status

2. View Requirement Status

You can check the Requirement Status in 3 areas:

2.1 View Requirement Status In The Requirement Detail Screen

You can view the Requirement Status in the Requirement Detail Screen by following these steps:

  1. On the left-hand side menu bar, navigate to the Classic Test section → Choose Requirements.

  2. Select the Requirement Key ID of the requirement you want to view the status.

CleanShot 2026-10-22 at 14.32.17@2x.png

  1. The Requirement Detail screen will open, where you can view the Requirement Status, reflecting the latest testing results linked to that requirement.

CleanShot 2026-10-22 at 14.38.17@2x.png

2.2 View Requirement Status In The Test Coverage Report

You can view the Requirement Status in the Test Coverage report by following these steps:

  1. On the left-hand side menubar, navigate to the Reports section.

  2. Select the “Test Coverage” report type.

CleanShot 2026-10-22 at 14.49.11@2x.png

  1. The report provides an overview of all requirements, displaying run status as percentage charts and detailed status information for each requirement.

CleanShot 2026-10-22 at 14.53.30@2x.png

The requirement status in this report depends solely on the Test Case scope and cannot be adjusted to the Test Script scope.

2.3 View Requirement Status In The Test Traceability Report

You can view the Requirement Status in the Test Traceability report by following these steps:

  1. On the left-hand side menubar, navigate to the Reports section.

  2. Select the “Test Traceability” report type.

CleanShot 2026-10-22 at 14.49.11@2x.png

  1. The report will display all active requirements, along with their latest run status.

CleanShot 2026-10-22 at 15.03.14@2x.png

The requirement status in this report depends solely on the Test Case scope and cannot be adjusted to the Test Script scope.

3. Requirement Status Explanation

The Requirement Status is calculated based on the statuses of its linked Test Cases and Test Script items, depending on the selected calculation scope.

When a Requirement has multiple linked Test Cases or Test Script items with different statuses, AgileTest determines the overall Requirement Status using the priority order below. The first matching rule takes precedence.

Priority

Requirement Status

Rule

1

UNCOVERED

  • No Test Cases or Test Scripts, and no Test Sessions are linked to the Requirement.

2

COVERED

  • At least one Test Session is linked, but no Test Cases or Test Scripts are linked.

3

NOK

  • At least one Test Case/Test Script is linked

  • At least one status maps to NOK available

4

UNKNOWN

  • At least one Test Case/Test Script is linked

  • No status maps to NOK available

  • At least one status maps to UNKNOWN available

5

NOT RUN

  • At least one Test Case/Test Script is linked

  • No status maps to NOK / UNKNOWN available

  • At least one status maps to NOT RUN available

6

OK

  • At least one Test Case/Test Script is linked

  • No status maps to NOK / UNKNOWN / NOT RUN available

  • At least one status maps to OK available.

Learn more:

Check how the default test statuses are mapped to requirement statuses.

Test Case Status

Meaning

Maps to Requirement Status

TO DO

The test has not started.

NOT RUN

BLOCKED

The test is blocked and cannot proceed.

NOT RUN

PASS

The test has passed.

OK

SKIPPED

The test was skipped.

OK

FAIL

The test has failed.

NOK

QUERY

The test has an open query to resolve.

UNKNOWN

RETEST

The test needs to be retested.

UNKNOWN

Example:

 

Test Case 1

Test Case 2

Test Case 3

Requirement Status

Scenario 1

Fail

Pass

To Do

NOK

Scenario 2

Skipped

Blocked

To Do

NOT RUN

Scenario 3

Query

Blocked

Fail

NOK

Scenario 4

Pass

To Do

Query

UNKNOWN

Scenario 5

Retest

Skipped

Blocked

UNKNOWN

Scenario 6

Pass

Retest

Query

UNKNOWN

Scenario 7

Skipped

Pass

Pass

OK

Custom Test statuses also follow this priority order based on their mapped to Requirement Status ( OK , NOK , NOT RUN , or UNKNOWN ).

 

Test Case 1

Test Case 2

Test Case 3

Requirement Status

Scenario 1

Critical Fail

(Custom status mapped to NOK )

Pass

To Do

NOK

Scenario 2

Skipped

Blocked

In Review
(Custom status mapped to UNKNOWN )

UNKNOWN

Scenario 3

Skipped

Pass

Waiting for update

(Custom status mapped to NOT RUN )

NOT RUN

Explore how Requirement Status is calculated under:

 

Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!