Analysis & Scope Calculation
Agile Test makes it easy to analyze the state of the Requirements.
The coverage status is calculated for different analysis scopes. When the analysis scope is changed, the status is automatically recalculated for the new scope.
Reminder:
The requirement’s run status is determined by its links to test cases and test scripts.
A linked test session does not impact the requirement’s run status.
1. Overall Requirement Status
A Requirement run status is calculated based on its link with Test Cases and Test Scripts. In other words, only Test Cases and Test Scripts run status (depicted as 1) affect the run status of the Requirements (depicted as 2).
Below are the scenarios of how the Requirement run status is calculated (the effect of Test Sessions on Requirement run status)
Test Cases | Test Scripts | Test Sessions | Requirement run status |
|---|---|---|---|
N/A | N/A | N/A | Uncovered |
N/A | N/A | Available | Covered |
*N/A: Not Available
The Requirement run status will be calculated as COVERED if users choose to use only Test Session feature (exploratory tests) based on a requirement.
2. Requirement Run Status
The requirement status is determined as follows:
UNCOVERED
If no test case or test script is added to the requirement, the requirement’s run status will result as UNCOVERED.
Test Cases | Test Scripts | Test Session | Overall Run Status | |
|---|---|---|---|---|
Linked with | 0 | 0 | 0 | Uncovered |
COVERED
If a test session is linked to a requirement, it will update the requirement’s run status to COVERED , even if there’s no specific test case or test script linked to it.
Test Cases | Test Scripts | Test Session | Overall Run Status | |
|---|---|---|---|---|
Linked with | 0 | 0 | 1 | Covered |
NOT RUN
If a test case and test script are added, but no test run has been executed for those tests, the requirement is marked as NOT RUN.
The TO DO status does not impact the requirement’s run status; if the test is marked as TO DO and there is no other run status, the requirement will be marked as NOT RUN.
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Run Status | No Test Run | No Test Run | Not Run |
SKIPPED
SKIPPED status will not affect the requirement run status.
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Example 1 | Skipped | Pass | Pass |
Example 2 | Fail | Skipped | Fail |
UNKNOWN
In case there are no FAIL and TO DO tests, if there is any QUERY , RETEST , or BLOCKED test, the requirement's run status will be considered as UNKNOWN.
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Example 1 | Skipped | Query | Unknown |
Example 2 | Pass | Retest | Unknown |
Example 3 | Blocked | Pass | Unknown |
OK
If all tests are PASS or SKIPPED , or a combination of PASS and SKIPPED, the requirement will be considered OK .
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Example 1 | Skipped | Pass | OK |
Example 2 | Pass | Pass | OK |
Example 3 | Skipped | Skipped | OK |
NOK (FAIL)
If there is any FAIL test, the requirement will be considered as NOK.
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Example 1 | Skipped | Fail | NOK |
Example 2 | Pass | Fail | NOK |
Example 3 | Fail | Blocked | NOK |
NOT RUN
If there is any TO DO test and no FAIL test, the requirement will be considered as NOT RUN
Test Cases | Test Scripts | Overall Run Status | |
|---|---|---|---|
Example 1 | To Do | Pass | Not Run |
Example 2 | Skipped | To Do | Not Run |
Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!