Test Coverage

While testers may be doing their best while designing and executing tests, there needs to be a way to identify the possible gaps. Test coverage reports help with verification whether every requirement has its own test case, which will be later on used to test the software. If there are any gaps present - they are a clear indication that some features may not be fully tested and will not comply with the requirements. With these reports, the QA teams can make more informed decisions while creating test cases and improve the end-product by reducing the risk of defects showing up later on.

Just like the Traceability Reports, the Test Coverage ones are to be accessed through the Testing Hub.

Creating Test Coverage Reports

1. In order to start generating the Test Coverage Report, go into Testing Hub > Report Design.

1. Select Test Coverage Report.

1. In the new dialog, select the Testing Setup, based on which ATM will generate the report.

   1. Users can use JQL syntax to narrow down the Requirements scope that is taken into consideration when creating the report, e.g. to report on Requirements with status 'Accepted'.

1. To finish, click Generate the report.

Test Coverage View

The generated Report consists of information panels at the top and a table below. The panels display following information:

• Testing Setup details

  • regarding the Testing Setup used in the Report

• Coverage of Requirements

  • covered Requirements are ones with linked Test Cases

In the table below, the users can find such Requirements details as:

• Work-key

• Summary

• Assignee

• Priority

• Status

Each of the Requirement listed within the Report can be accessed quickly by clicking on the work-key.