The project administrator can choose which of the available issue types should be handled as testable/coverable entities by dragging them to the corresponding target box. 

A testable/coverable entity is an issue that you can can cover with tests in order to validate its acceptance criteria. It can be a Story, Epic, Bug or any custom issue type you may have.

Note that you can also cover your defects (e.g., Bug) with tests, as long as you configure them as Coverable Issue Types.

Example of a possible setup

Test Coverage Hierarchy

In this section, you can define how Requirements and Sub-Requirements are associated. If the Jira link mechanism is used, then the Issue Link Type Direction must be chosen as well as the direction from the parent requirement to the child requirement. If Sub-Tasks are used, then simply check the Issue - Sub-Tasks relation option. Note: The Sub-Task requirement issue types must also be associated with "Requirements" in the Project Settings: Test Coverage section. 

Use Epic - Stories relation

When this option is enabled, Story issues are associated with Epic issues as Sub-Requirements.

Issue - Sub-Tasks relation

When this option is enabled, Sub-Requirements are associated with Requirements by Sub-Task Issues. When this option is disabled, Sub-Requirements are associated with Requirements with issue link configurations below.

Issue Links relations

A specific Issue link type for the Requirement -> Sub-Requirement relationship.

Issue Link Type Direction

Select the Link Direction for the parent -> child relationship of the Requirement -> Sub-Requirement.

For more information on the Requirement Status and coverage calculation, please refer to the Coverage Analysis.

  • No labels