Understand Java unit test coverage; Identify risk
Cover Reports delivers valuable insights about your Java codebase. It visualizes the state of unit testing and pinpoints unique, actionable insights that improve quality and efficiency. Granular unit test coverage reports - extending down to method level - are supplemented by information on variables like code quality, testability and complexity, for a more holistic view of unit testing.
Cover Reports provides a range of tables and dashboards that make it easy to understand coverage levels. It’s simple to drill down from a project-level overview to specific packages or classes.
Cover Reports allows Java teams to identify gaps in unit test coverage and the reasons for them. With Cover Reports you can realize more value from unit testing by understanding exactly where risk lies and what to do about it. Target available development resources more precisely to improve code quality faster and reduce the risk of regressions.
Cover Reports delivers granular coverage reporting that gives you more than a simple percentage. The insights it provides are based on the deep code analysis executed as part of Cover Core’s unit testing writing capability.
Coverage is an imperfect proxy for risk. Cover Reports also shows you exactly what code isn’t tested, how important it is, and why tests might not have been written. A Risk Index score provides a quick way to see what’s most important.
The insights provided by Cover Reports allow scarce developer expertise to be targeted more efficiently, either at areas of most risk or those where additional coverage can most easily be delivered.
With Cover Reports you can record and benchmark the effectiveness of your Java unit testing over time. For the first time it’s possible to track progress and the impact of change on coverage, across teams, applications and projects.
Cover Reports can be used to show how Diffblue Cover is being used in your organization - something that isn’t always easy when hundreds of developers, millions of lines of code and an automated CI pipeline are involved.
Cover Reports provides a range of dashboards which visualize unit test coverage and related risk. This project-level example shows that 33% of the code is not covered by unit tests; related risk has been assessed as 30/100.
Projects can be represented as granular treemaps which show coverage in different part of an application.
Changes in unit test coverage can be tracked over time to measure progress.
Diffblue Cover creates suites of unit tests that run in your continuous integration pipeline between versions and protect against regressions, so you can catch errors faster and earlier in the software development lifecycle. To learn more, see our our product page.
Diffblue Cover helps your team increase automation of your CI pipeline.
For development teams, this:
For DevOps teams, this:
Yes. Diffblue Cover quickly generates tests that will allow you to adopt CI. The generated tests will help developers quickly identify regressions in subsequent commits before committing new versions.
See the product datasheet for more information.
Diffblue regression suites are maintained automatically and updated with each new code version to capture the current behavior of the code.
Diffblue Cover AI analyzes your code and writes Java unit tests that run in a CI pipeline after each commit. Cover’s tests:
No. Diffblue Cover is meant to complement your own unit tests and help you catch regressions.
Developers write individual unit tests to test specific functionality. Diffblue regression suites are generated automatically to help find regressions early in the development cycle. Find out more in our Unit Regression Tests eBook.