Versions Compared

Key

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

Table of Contents


The project administrator  administrator can choose which of the available issue types should be  be handled as testable entityies, /coverable entities by dragging the available issue types 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.

Image AddedImage Removed

Example of a

...

possible setup

Image RemovedImage Added

Test Coverage Hierarchy

...

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 links configured link configurations below.

Issue Links relations

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

...

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



Info

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