AgileTest

Test Case Calculation Scope

Test Case Calculation Scope means AgileTest uses the test cases linked to a requirement to determine the requirement's status. Only linked test cases and the status of their latest relevant run within the selected scope are used.


1. How test statuses map to requirement statuses

1.1 Default test statuses

There are 7 default Test Case statuses, each with a fixed mapping that cannot be modified.

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

1.2 Custom test statuses

In addition to the 7 default Test Case statuses, you can create custom statuses and map each one to a Requirement status. This mapping determines how Test Case results contribute to the overall Requirement status.

  1. Go to Settings → Marketplace apps.

CleanShot 2026-10-20 at 16.11.56@2x-20261020-091231.png
  1. Select the AgileTest app and choose Test Statuses.

  2. Click the “+ Test Status” button.

CleanShot 2026-10-20 at 16.09.13@2x-20261020-091007.png
  1. Enter the name, description, and color.

  2. In Requirement status, choose UNKNOWN NOK NOT RUN OK . New statuses default to UNKNOWN .

CleanShot 2026-10-20 at 16.14.31@2x-20261020-091628.png

If you change the mapping of a custom status, requirement statuses and reports use the new mapping right away.

COVERED and UNCOVERED cannot be chosen for a test status. They depend only on what is linked to the requirement.

2. Apply Test Case Scope

2.1 Apply Test Case Scope

To apply Test Case Scope for the Requirement Status calculation, follow these steps:

  1. Choose the Test Cases tab in the Requirement Detail Screen.

  2. Click the “Analysis & Scope” box.

CleanShot 2026-10-22 at 10.42.47@2x.png
  1. Select the “Test Case” scope. You can apply filters to limit the test cases included in the calculation

  • Test Environments: Filters test cases based on the environment where they are executed, such as Development, Staging, or Production. This helps you calculate the requirement status using results from a specific environment only.

  • Version: Filters test cases by the application version being tested. This is useful when you want to evaluate the requirement status for a particular release or build.

  • Test Plan: Filters test cases that belong to a specific test plan. This allows you to calculate the requirement status based on the testing scope defined in that plan.

  1. Click the “Apply” button to calculate the Requirement Status.

image-20261020-092308.png

2.2 How AgileTest Determines Each Test Case Status

For each linked Test Case, AgileTest uses the latest Test Executions that match your selected scope and filters to calculate the Requirement Status.

  • If multiple Test Executions match: AgileTest uses the most recent run based on its finish time, or last updated time if it is not finished.

  • If a matching Test Executions exists: AgileTest maps its status to the corresponding Requirement Status ( UNKNOWN NOK NOT RUN or OK ).

  • If the test case has not yet been executed in any executions: AgileTest counts as TO DO , so it maps to NOT RUN .


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