The User Story Coverage Report empowers managers to allocate resources effectively and achieve high-quality releases. Learn how to harness the report for data-driven resource prioritization.
Step-by-Step Tutorial
1. Access the Report
Navigate to your relevant Jira project and locate the User Story Coverage report within the Sheets page.
Simplify View: Collapse subtasks under user stories (or your hierarchy) for better visualization.
Review Metrics: Analyze both Modified Coverage and Non-Unit Tests Coverage for each user story.
4. Identify Gaps
Focus on Low Coverage: Expand user stories below 100% to pinpoint specific subtasks lacking tests.
Verify Satisfactory Subtasks: For sufficiently covered subtasks, ensure alignment with your testing strategy (e.g., API testing for relevant changes).
Address Specific Test Types: For stories with 100% overall coverage, assess individual test type coverage against your standards. Identify responsible subtasks for any deficiencies.
5. Craft a Testing Plan
Categorize Gaps: Create separate lists for:
Uncovered subtasks.
Subtasks with low coverage.
Subtasks lacking crucial test types (based on your strategy).
Assign Ownership: Match each list item with its parent user story for context.
6. Prioritize Resources
Strategic Allocation: Follow this sequence:
Address uncovered subtasks first, as they represent complete testing absence.
Move to subtasks with low coverage, prioritizing based on severity and impact.
Assign relevant individuals to cover subtasks within critical test types, focusing on sensitive code sections and those containing critical functionality.
Remember: This framework serves as a foundation. Adapt it to your specific organizational needs, testing strategies, and resource availability.
