.png)
Test Script Calculation Scope means AgileTest uses the test scripts linked to a requirement to determine the requirement's status. Only linked test scripts and the status of their latest relevant run within the selected scope are used.
1. How Test Run Item statuses map to Requirement Statuses
There are 6 default Test Run Item statuses, each with a fixed mapping that cannot be modified.
|
Test Run Item Status |
Meaning |
Maps to Requirement Status |
|---|---|---|
|
TO DO |
The item has not started. |
NOT RUN |
|
BLOCKED |
The item is blocked and cannot proceed. |
NOT RUN |
|
PASS |
The item has passed. |
OK |
|
SKIPPED |
The item was skipped. |
OK |
|
FAIL |
The item has failed. |
NOK |
|
QUERY |
The item has an open query to resolve. |
UNKNOWN |
Note:
Custom Test Statuses apply to test case runs only. Test script run items always use the fixed statuses above, so this mapping cannot be changed.
2. Apply Test Script Scope
2.1 Apply Test Script Scope
To apply Test Script Scope for the Requirement Status calculation, follow these steps:
-
Choose the Test Scripts tab in the Requirement Detail Screen.
-
Click the “Analysis & Scope” box.
-
Select the “Test Script” scope.
-
Click the “Apply” button to calculate the Requirement Status.
2.2 How AgileTest Determines Each Test Run Item Status
For each linked Test Script, AgileTest uses the latest Test Runs that match your selected scope to calculate the Requirement Status.
-
If multiple Test Runs match: AgileTest uses the most recently created test run.
-
If a matching Test Run exists: AgileTest maps its status to the corresponding Requirement Status ( UNKNOWN NOK NOT RUN or OK ).
-
If the test script item has not yet been executed in any runs: AgileTest counts as TO DO , so it maps to NOT RUN .
Learn more
Check how AgileTest requirement statuses are calculated.
Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!