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.

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.

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.

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.

 SKIPPED

SKIPPED status will not affect the requirement run status.

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.

 OK

If all tests are PASS or SKIPPED , or a combination of PASS and SKIPPED, the requirement will be considered OK.

NOK (FAIL)

If there is any FAIL test, the requirement will be considered as NOK.

NOT RUN

If there is any TO DO test and no FAIL test, the requirement will be considered as NOT RUN

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