Page History
...
Tests and coverable issues (e.g. requirements) can be analyzed from different perspectives/scopes.
...
In fact, Tests and coverable issues can be analyzed from these scopes (or dimensions):
- None (latest execution) No Version (i.e. latest results)
- Version
- Test Plan
Besides these scopes, they can also be analyzed based with some additional criteria that will affect the calculated values:
- Test Environment
- Final statuses precedence over non-final ones
...
None (latest execution)
If you don't care about versions, or are not using versions at all, and just want to see the calculated statuses based on the latest runs, analysis by Version "No VersionNone (latest execution)" can be used for that purpose.
...
Within the issue screen, the coverage status can be evaluated for the specified scope within the Test Coverage section. The calculated coverage status is shown on the right side.
Reports
Overall Requirement Coverage
...
The Test Sets, and implicitly the Tests within them, can be analyzed for some given scope using the Test Sets List report.
Troubleshooting
"I have an Xray Project to Test my Requirements project. I've created a Test and I have already executed the Test, but I always get requirements status Covered but Not Run."
| Warning |
|---|
You might be using environments on Test Executions that are affecting the aggregated status for the Tests. If you have a couple of Test Executions, one with a specific environment (e.g., Android) and another without any environment, then Xray will also consider the empty environment when calculating the aggregated status (this is, of course, if all Test Executions are within the same Version or Test Plan). |
...