Selective unit test execution for faster, cheaper Java development
Diffblue Cover Optimize enables faster, cheaper, more flexible delivery of Java code by minimizing the time needed to run unit tests, whether on the developer desktop or in a Continuous Integration (CI) pipeline.
Running an entire unit test suite every time a change is made may mean executing hundreds, or even thousands, of unnecessary tests with no connection to the change - a waste of time and money that prevents developers from getting fast feedback.
Cover Optimize automatically selects the only the JUnit tests required to fully validate that a code change hasn’t introduced regressions, slashing test execution time to accelerate development cycles and increase team productivity.
Optimize leverages the automated analysis and unit test writing capability provided by Cover’s core AI for Code engine to make this selection.
Running every unit test every time, whether relevant or not, is highly inefficient. Selective test execution for each PR means changes can be refined and deployed more quickly.
Waiting time is wasted time. Optimize means developers spend less time waiting to see whether code changes pass unit testing, and reduces disruptive context switching.
Faster testing can also have direct cost benefits: in cloud-based systems with consumption-based billing running fewer tests might literally mean smaller bills.
Effective testing is recognized as one of the biggest blockers of fast, agile software development, especially in large applications. Optimize helps make testing more efficient.
The deep code analysis delivered by Cover’s core unit testing writing capability provides the information Optimize uses to determine which tests matter for each code change.
Diffblue Cover Core uses comprehensive analysis of your code’s behavior to automatically create and maintain high levels of unit test coverage. This analysis provides the insight Optimize needs to determine which tests matter to each code change.
Diffblue Cover integrates into your CI pipeline to make unit testing an automated, efficient, effective part of the process. Cover Optimize means that only the tests related to each PR are run when code changes are made.
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.
See our case study on how Goldman Sachs has benefited from using Diffblue Cover to increase coverage and create a safety net against regressions.
For example of other ways our customers use Diffblue Cover, click here.
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.