How do you track test coverage in Agile?

1 Choose the right metrics

There are different types of test coverage metrics, such as code coverage, requirement coverage, and user story coverage. Each one has its own advantages and limitations. For example, code coverage tells you how much of your code is executed by your tests, but not how well your tests check the logic and behavior of your code. Requirement coverage tells you how many of your requirements are tested, but not how well your tests match the expectations and needs of your stakeholders. User story coverage tells you how many of your user stories are tested, but not how well your tests cover the acceptance criteria and scenarios of your user stories. Depending on your project context and goals, you may need to use one or more of these metrics, or even create your own custom metrics, to track test coverage in Agile.

2 Integrate test coverage tools

To track test coverage in Agile, you need to use tools that can automate the collection and analysis of test coverage data. These tools should be integrated with your development and testing tools, such as your IDE, your version control system, your test management system, and your continuous integration and delivery pipeline. This way, you can get real-time feedback on your test coverage, and identify any gaps or risks that need to be addressed. Some examples of test coverage tools are JaCoCo, Cobertura, SonarQube, TestRail, and Zephyr.

3 Review test coverage regularly

Tracking test coverage in Agile is not a one-time activity. It is a continuous process that requires regular review and improvement. You should review your test coverage at different levels and stages of your Agile project, such as during sprint planning, daily stand-ups, code reviews, sprint reviews, and retrospectives. You should also compare your test coverage with your quality goals and standards, and adjust your testing strategy and plan accordingly. For example, you may need to add more tests, refactor existing tests, prioritize high-risk areas, or remove redundant or obsolete tests.

4 Communicate test coverage clearly

Tracking test coverage in Agile is not only a technical task. It is also a communication task. You need to communicate your test coverage clearly and effectively to your team members, stakeholders, and customers. You need to use visual and interactive reports and dashboards that can show the status and progress of your test coverage, as well as highlight any issues or concerns. You need to use common and consistent terminology and definitions that can avoid confusion and misunderstanding. You need to use test coverage as a means to enhance collaboration and transparency, not as a means to blame or judge.

5 Use test coverage as a guide, not a goal

Tracking test coverage in Agile is a useful and valuable practice, but it is not an end in itself. Test coverage is a guide, not a goal. It can help you assess and improve the quality of your software, but it cannot guarantee it. Test coverage can show you what you have tested, but not what you have missed. Test coverage can indicate the quantity of your tests, but not the quality. Therefore, you should not rely on test coverage alone, or aim for a specific percentage or threshold, as a measure of your testing success. You should also consider other factors, such as customer feedback, defect rates, user satisfaction, and business value, to evaluate and enhance your testing performance.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?