Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Test Coverage view shows all tests associated with the Requirement Covered Issue (e.g. Story, requirement) and their respective Requirement status for the chosen filteranalysis scope. In this view, you can create a new Test and associate it with the Requirement Covered Issue or just associate an already existing Test with the Requirementit.


Test Coverage Analysis

The Requirement status for each Test can be filtered by the following categories:status of the covered issue and of the linked Tests can be analyzed from multiple perspectives/scopes.

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.

...


Latest

Version

In the version category, it is possible to see the Requirement Status for each of the project's versions.

...

In the test plan category, it is possible to see the Requirement Status for each of the Test Plans. 

Test Environment

It's possible to see the status of each Test based on the Test Environment you chose in this option.

...

To create a new Sub Test Execution from the RequirementCovered Issue, containing all linked Tests:

...