Page History
...
| Table of Contents |
|---|
Analysis Scopes
The status of the covered issue and of the linked Tests can be analyzed from multiple perspectives/scopes.
Tests and coverable issues can be analyzed from different perspectives/scopes.
...
Besides these scopes, can also be analyzed for some
- Test Environment
- Final statuses precedence over non-final ones
Latest
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 "Latest" can be used for that purpose.
This may be useful to have a quick idea about the latest results or calculated status for the Test or coverable issue.
Please note that whenever analyzing by latest results also considers the latest results made for the different environments (i.e. when "All Environments" is selected as Test Environment).
Version
The "Version" scope allows users to analyze Tests and coverable issues from a version perspective and answer questions such as "How is the requirement on version X?", "How are these Tests performing on version Y?".
Whenever analyzing by version, only Test Executions made for the given version are considered, through the Test Execution's Fix Version field.
As an example, a user story aimed for version 3.0 may be analyzed from the point of view of the executions made for version 3.0 or for the ones made afterwards on version 4.0.
Test Plan
Analysis by Test Plan gives the ability to evaluate the Test status or coverage status based on some planned testing (i.e. on the Tests and related executions made in the scope of the selected Test Plan).
Whenever analyzing by Test Plan, only Test Executions linked to that Test Plan are considered.
This kind of analysis provides to means to evaluate if a given coverable issue is covered or not by the Tests of some Test Plan and, if so, how it is based on the executions performed from the related planned Test Executions.
Test Environment
Analysis by Test Environment gives the ability to analyze the Test status or the coverage status of an issue for some Test Environment.
This kind of analysis gives the abilitty to answer questions such as: "How is this requirement on the environment X?", "How is the Test
Whenever analyzing by Test Environment, only Test Executions made for the given Test Environment are considered.
Final Statuses Precedence
Final statuses precedence is used to perform the analysis based on "finished work" (non intermediate Test Runs).
The flag "Final statuses have precedence over non-final statuses" gives the additional ability to consider just Test Runs whose status is one configured as being a final status.
This helps answer questions such as: "Which is the latest
As an example, a user story aimed for version 3.0 may be analyzed from the point of view of the executions made for version 3.0 or for the ones made afterwards on version 4.0; it can eventually be analyzed by taking into account the Tests and Test Executions linked to some Test Plan. Of if you don't care with exact versions and just want to see the calculated statuses based on the latest runs, analysis by "Latest" can be used for that purpose. Another analysis dimension is the Test Environment; if chosen, then only executions made for that Test Environment are considered for the shown statuses.
Analyzing Xray entities
Xray entities can be analyzed in different places, starting with the issue view screen and also in some specific reports containing those entities.
...