Page History
...
UI Steps | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Analysis
On the left side (section A), it's possible to define the analysis strategy, i.e., the way you want to analyze the selected/filtered requirements. You can choose to analyze either by Version or Test Plan, and complement it with a Test Environment.
If you choose analysis by Version, then only the Test Executions for the specified version are taken into account.
If you choose analysis by Test Plan, then only the Test Executions (and related Tests and results) for the given Test Plan are considered for the calculation of the coverage status of each requirement.
If the Test Environment is specified, then it considers only the executions within that Environment.
Info | ||
---|---|---|
| ||
When you choose analysis by Test Plan, the requirements are not filtered in any way. Therefore, if you want to restrict the list of requirements that are being shown (e.g., just show the requirements being indirectly covered by the Tests belonging to a Test Plan), you must always use the Filter options and eventually, some saved filter for that purpose (such as the testPlanRequirements JQL function). |
Understanding the report
|
...
Requirements
...
Test Runs
...
defects directly associated with the Test Runs as well as those directly linked to the Tests (via a "created" issue link) for the given version (through the AffectsVersion).
Info | |||
---|---|---|---|
| |||
The defects that appear on a separate
|
Examples
...
In the following example you can see the hierarchical relation between an Epic and some Stories (hierarchical presentation should be enabled in the report settings - section D).
|
...
|
...
|
...
|