Page History

A coverable (i.e., or testable) issue , is one whose issue type is configured at the project-level settings to be handled as coverable issue type (more info in Project Settings: Test Coverage).

Typically, issue types such as Epic, Story may be configured to be handled as coverable issue types. However, the project administrator can define exactly which issue types can be handled in this way.

Coverable . These issues can be covered/validated by Tests (either manual or automated). Tests can then be organized (i.e., in Test Sets), planned (i.e., in Test Plans) and executed (i.e., in Test Executions). The results obtained for the linked Tests will affect the calculation of the test coverage status of the covered issue.

Typical examples include Epic and Story, but your project administrator can define exactly which types can be handled in this way. For more info, check outProject Settings: Test Coverage.

Test Coverage View 

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

...

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 ). You can take into account the Tests and Test Executions linked to some Test Plan. Of On the other hand, if you don't care with about exact versions and just want to see the calculated statuses based on the latest runs, you can use analysis by "Latest" can be used for that purpose. Another analysis dimension is the Test Environment; if chosen, then only the statuses of the executions made for that Test Environment are considered for the shown statuses.

Please read Coverage Analysis for a more detailed explanation on how to perform coverage analysis and to find out the places where you can perform it for the different entities.

...

Latest

Version

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

Test Plan

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

Test Environment

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

Actions

Create new Test

To create a new Test from the Requirement:

1. 1. 1. Click the Create new Test optionTest.
         
      2. The Jira issue dialog will appear giving the ability to create the Test case.
         
      3. After filling Fill out the fields, the . The Test issue will be created using the default Test Type, as configured in Project Settings: Test Types.
         
      4. Finally, you can add the remaining information for the Test (e.g., the steps, in case the Test is of kind "Manual").

...

To associate an existing Test/Test Set with the Requirement:

1. 1. 1. Click on the Link  option Link.
         
      2. The Jira Issue link dialog will appear. Make sure to selected select the correct link type (e.g., "is tested by") along with the issue key of the Test(s)/Test Set(s).
         

Create new Sub Test Execution

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

1. 1. 1. Click the Create new Sub Test Execution optionExecution.
         
      2. The Jira issue dialog will appear giving the ability to create the Sub Test Execution. Fill out the form and click Create.