Page History
...
- Obtain the list of Tests that directly or indirectly through Sub-Requirements (info here) cover the requirement
- This depends on the Requirement Coverage configuration
- Calculate the Test status for all the Tests individually, in version V or Test Plan TP
- This takes into account Test Runs in version V (as a result of Test Executions in version V) or Test Runs in Test Plan TP (within Test Executions associated with Test Plan TP)
- If a specific Environment is also chosen, then only Test Runs from Test Executions with this Environment will be considered. In case no Environment is specified then all Test Executions are considered (more info here).
- Calculate the "joint" status of all the previous Test statuses (i.e. by comparing together each Test status)
- Calculate the requirement status mapped to the previous calculated Test status
...
- the requirement coverage strategy defined in the respective setting, in Xray administration settings, in the tab "Requirement Coverage" (more info here)
- the strategy is used to find out the relevant Tests considered for the calculation
- the separation of concerns setting, in Xray administration settings, in the tab "Requirement Coverage" (more info here)
- this affects how the status of a Test Run contributes to the status of each linked requirement; if disabled, users can enforce a specific mapping for each requirement, otherwise the Test Run status will contribute in the same way to all the linked requirements
- indirectly, the setting "Final statuses have precedence over non-final statuses" in Xray administration settings, in the tab "Test Statuses" (enabled by default)
- the existence of Test Runs for different Test Environments, in case the analysis is made for "All Environments"
...
When a requirement has some sub-requirements, then the calculated status for the parent requirement depends not only on its status calculated per -si se but also on the status of each individual sub-requirement.
...