Page History
Anchor | ||||
---|---|---|---|---|
|
Table of Contents |
---|
Info | ||
---|---|---|
| ||
Please read Understanding the calculation of coverage status and the status of Tests for an in-depth explanation of the calculation of these statuses. |
...
- "What is the current status of this requirement (or test)?" (if final statuses precedence is unchecked)
- "What is the status of this requirement (or test), considering just the finished work?" (if final statuses precedence is checked)
...
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
Test Coverage
Coverable issues can be analyzed for a given scope using the Test Coverage report. More info about this report in Test Coverage Report. The chosen scope will be store in the user preferences, and will affect all issues in the same project.
Tests
The status of Tests can be evaluated directly in the Test issue view screen as well as on some reports, including the Tests List report and, indirectly, the Test Sets List report.
...
Within the Test issue screen, the Test status can be evaluated for the specified scope. The calculated status is cached for performance reasons. Since data between Jira and Xray may not be in sync, it's possible to enforce a recalculation to display an up-to-date value. The chosen scope will be store in the user preferences, and will affect all issues in the same project.
Reports
Tests List
The Tests can be analyzed for a given scope using the Tests List report.
Test Sets
The status of Test Sets (i.e., of the Tests contained within a Test Set) can be analyzed using the Test Sets List report.
...
The Test Sets, and implicitly the Tests within them, can be analyzed for a given scope using the Test Sets List report.
Troubleshooting
...
Warning |
---|
You probably have not configured your versions properly. Remember that coverage status of some issue for some version is calculated based on the Fix Version associated with the Test Execution issues. |