10X: Sprint Coverage

About this report

The Sprint Coverage report displays a list of stories and their associated acceptance criteria and test cases for a selected sprint within a PI. Use this report to track acceptance criteria and test case coverage in a sprint. Click on any story in the list to open the Story panel and access a story's test cases and acceptance criteria.

This report can be used by Scrum Masters, team and QA managers, and QA/development staff to make sure each story in a sprint has proper coverage of test cases and acceptance criteria. It is beneficial to review the report with team members during daily standup and sprint review meetings.  

Navigation

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

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. Acceptance criteria should be created for stories. 
  5. Test cases should be created for stories.

How are report values calculated?

  1. Stories for the selected PI are pulled from the Story page.
  2. Acceptance criteria and test cases are pulled from values entered on the Story panel for an individual story. 

Sprint_Coverage.png

How to interpret this report

Tracking test cases in a sprint can help determine which portions of the code are actually being tested, as well as the parts that cannot be tested if test cases do not exist--which 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. You can also look for meaningless test cases that do not increase coverage and remove them from a story.

Tracking acceptance criteria in a sprint is equally important. Acceptance criteria are the conditions that a software product must satisfy to be accepted by a customer. Ideally, each story will have multiple acceptance criteria that ensure a higher level of quality and customer satisfaction. If you find stories that do not have corresponding acceptance criteria, you should consider adding the criteria immediately, before development work begins.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.