Page History
The options available in Requirement Coverage are:
| Table of Contents |
|---|
| Note |
|---|
A JIRA Jira re-index recommended is suggested when recommended if there are changes to the Requirement Coverage options. |
...
The requirement coverage strategy defines how the Requirement Status must be calculated. The following strategies are available:
...
When this option is enabled, Requirement Tests must be associated with Test Sets of a specific Fix Version to be considered for the Requirement Coverage of that particular version. A given Test T is considered for requirement coverage of Requirement R in the version V if:
...
Once Test T is considered for coverage in version V, it's its Status is calculated based on the latest Test Run with the specified Fix Version V.
| Info | ||
|---|---|---|
| ||
Please see more info in the page dedicated to Requirements Coverage Analysis in the User's Guide. |
Ignore Requirements with Status
...
When this option is checked, the result of a Test will affect all Requirements that are associated with it. Uncheck this option if a single Test result affects multiple Requirements in different ways and these might have different statuses depending on specific steps. This will allow you to manually set the affected Requirement statuses for each Test Run on the execution screen. The calculation of the Requirement Status calculation will then consider these Requirement statuses explicitly.
| Info | ||
|---|---|---|
| ||
Test T1 is associated with Requirements R1 and R2:
|
Include Previous Version Requirements
...