Test Coverage

Owned by Support Advocate (ease solutions)
Last updated: Dec 15, 2022 by Angelica Salazar
2 min read

 

Test Coverage views help you to understand the connection between test cases and other sorts of issues, such as requirements. Most importantly, a coverage view helps you to understand how extensive your test case coverage is. For example, it allows you to see which requirements are now covered by test cases and which are not yet covered. It can also show other connections, such as bugs that arise from executing test cases. A test coverage view also optionally shows the results of the last test runs.

You can have as many different test coverage views as you need for your project. You have complete freedom in determining the issues displayed in a given view, since the contents are specified by Jira queries.

A test coverage view is organized as a table, with each cell representing an issue and the columns showing the issues relating to the issues in the preceding column. For example, the leftmost column could be customer requirements, the second column could be the test cases that are related to those requirements, and the third column could be the unresolved bugs discovered during the execution of the related test cases. Reading from left to right, you would see a customer requirement in the first column, the test case (or cases) related to it in the second column, and finally, in the third column, the bugs arising from the execution of the test cases. If a given requirement has no related test cases, you see an empty cell. (This lack of coverage is perhaps a cause for concern.) You also see an empty cell if a given test case has no unresolved bugs (probably a cause for satisfaction).

You can also optionally enable a column that shows a number of recent test executions associated with each case, allowing you a quick overview of how successful the testing is at a given time.

Each column of the table (except for the first and the test execution column) provides an indication of the degree of coverage.

The information provided for each issue in the table is configurable. The issue key, status and summary are always displayed, but additional fields can be selected for displayed.

Â