User Story Coverage Analysis
Last updated
Was this helpful?
Last updated
Was this helpful?
Was this helpful?
Explore Individual User Stories' coverage:
Subtask Coverage: Quickly identify coverage gaps and pinpoint areas needing attention for each subtask.
Method Coverage: Dive into a detailed list of modified methods per subtask, easily spotting uncovered methods requiring testing focus.
Ideally suited for developers and QA engineers to deep dive into the coverage of an individual user story, collaborate and make informed decisions regarding the prioritization and allocation of testing resources.
If the overall coverage is not satisfactory, the subtasks associated with the user story can provide a better understanding in which areas there is low or no coverage.
Once the uncovered subtasks are pinpointed, it is easy to examine their method level coverage. Attention should be focused on the methods that are marked orange or red, indicating insufficient testing. Methods of critical code segments (based on commit messages) will be flagged red if they have not been tested by all relevant test types.
This empowers teams to have efficient conversations, identify specific uncovered areas, and prioritize testing efforts effectively. This granular approach facilitates informed decision-making regarding the readiness of user stories for deployment and minimizes the risk of undetected defects.
To facilitate rapid evaluation of code coverage within our User Story Coverage Analysis, we implemented intuitive color indicators:
Red: Attention needed, coverage less than 20%
Orange: Room for improvement, coverage between 20% and 70%.
Green: Well-covered, exceeding 70% coverage.
These color indicators can be customized to suit specific project requirements. Additionally, methods marked as critical will appear red if they have not been tested by any test type, or orange if they have not been tested by any non-unit test type.