Test case coverage

About this report

The test case coverage report displays a cumulative count of stories created and story test cases created for a selected team within a PI. This report is in the form of a line graph, with the story/test case count on the Y axis, and the sprint dates for the selected PI on the X axis. Use this report to track test case coverage in a sprint/PI. 

This report can be used by Scrum Masters, team and QA managers, and QA/development staff to make sure stories in a sprint have adequate coverage of test cases. It is beneficial to review the report with team members during daily standup and sprint review meetings, as well as pre- and post-PI meetings. 

To navigate to this report:

1. Select Teams in the top navigation bar and select the team you want to view information about.
2. On the sidebar, select Reports in the list of options.
3. Select Test case coverage; the report displays.

Prerequisites

1. PI must exist in the system and be tied to a program.
2. Sprints must be created and tied to a PI. 
3. Stories must be created and tied to a sprint. 
4. Teams should be created and tied to a program.
5. Test cases should be created for stories.

How are report values calculated?

1. Story counts for the selected PI and team are pulled from the Story page.
2. Test case counts are pulled from values entered on the Story panel for an individual story. 

How to interpret this report

Tracking test cases in a sprint can help determine if portions of the code are actually being tested, as well as if parts cannot be tested because test cases do not exist. Test cases should help with the overall quality of your project. Ideally, each story will have test cases associated with it, which in turn will help keep time, cost, and scope in check. Therefore, the count of test cases should follow a similar trend as the count of stories--a low count of test cases indicates inadequate coverage, and should be rectified.