Coverage By Requirement

The Coverage By Requirement report displays the coverage relationship between Stories and Test Cases. For the selected Project, the Coverage Report shows which stories have one or more test cases associated with it. The requirement coverage is critical for the successful delivery of the project. Requirements, which are covered by/linked to a test case, are identified covered requirements.  

To view the report,

  1. Go to QMetry Menu > Test Management > Test Report tab.

  2. On the Test Report window expand Coverage Reports

  3. Select By Requirement

The Requirement filter in the report configuration supports JQL that allow users to use multiple fields like Project, Issue Type, Issue Status, etc. as filter to generate the report. Write JQL query to construct the story selection criteria with different filters. You can save the applied Filter and add it as a  gadget on the dashboard. You can refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4JS/pages/1210847699 and https://qmetrysupport.atlassian.net/wiki/spaces/QTM4JS/pages/1210847652 for more details.

Note: The report gets updated dynamically if new stories are added matching the selection criteria.

 

The chart displays Story Coverage based on test cases within the selected stories.

  • Covered: It refers to Stories which have test cases linked within it.

  • Not Covered: It refers to Stories which don’t have any test case linked within it.

The report is available in graphical format as well as in tabular format. To view the details in tabular form, click on the table icon above the graph.

Export Coverage Report

The report can be exported in XLS format. It provides details of stories bifurcated on the basis of types of test cases within it.

The exported report displays whether the story is Planned/Unplanned and the coverage is Manual/Automated.

  • Manual Coverage: It refers to Stories which have Manual test cases linked within it.

  • Automation Coverage: It refers to Stories which have only Automation test cases linked within it. Linking the automated Test cases with Story is supported only with Cucumber and QAS framework.

  • Planned: Test cases those are linked with test cycles are "Planned" for execution. 

  • Unplanned: Test cases those are not linked with test cycles are considered "Unplanned" for execution.