There is a lot more to coverage than a number you share with your management team. Even code with high coverage can leave critical gaps, while your voluminous non-critical code buffers the percentage, leaving your code base vulnerable to risk. We define code risk as a combination of factors including code quality, complexity and coverage. Unfortunately, we often lack visibility into where this risk is within our codebase.  

To ensure our customers have coverage where it’s most important, we’re introducing new data visualization reports for the Diffblue Cover CLI. These reports will unlock insights about your code down to the method level with surgical precision and identify gaps in your application’s coverage to target your team’s development work. 

Introducing the Diffblue Cover reports

Your reports dashboard will give you an overview of your total code coverage and a test coverage breakdown.  In this report, you will be able to see how much of your code has been covered by manually-written tests and what percentage of coverage Diffblue Cover has provided. 

More importantly, you will see how much of your code was not tested or could not be tested by Diffblue Cover. This may signify that some of your code requires refactoring to become testable and lower your overall code risk. 

The coverage report will allow you to dive deeper into your codebase and assess coverage for classes and methods in your application. Here you may identify critical areas of your code that have disproportionately less coverage than your application overall, essentially allowing you to pinpoint exactly where your development team needs to spend time writing tests or refactoring. 

Getting Started with Diffblue Cover Reports

These reports are available now for all customers. To gain access, reach out to your account manager. If you aren’t already using the Diffblue Cover CLI, you can sign up for a free trial to get started.

Or to learn more, visit our product documentation.