Clover
Features – Test Optimization
Streamline your automated testing process to build quicker and more frequently.
Test only what you need
Clover has the ability to optimise test runs, greatly reducing the time it takes to test a code change. Since Clover tracks per-test coverage, Test Optimization automatically determines the optimal subset of tests to run based on the specific changes made. This avoids having you wait for the entire test suite to run for small changes, or even worse, not testing your changes at all. Testing only what you need provides quick feedback without compromising test quality.
Let Clover decide which tests to run
Optimise tests in your IDE
Running your entire test suite locally in your IDE is effective, but for small code changes it can take way too long. Typically, this leads developers to perform ad hoc testing or, even worse, no testing at all.
With Test Optimization available for both Eclipse and IntelliJ IDEA, Clover will automatically run selective testing so you don't have to wait for the entire test suite to run or risk omitting a critical test. Since shorter test runs provide faster feedback, you are more likely to end up testing your changes more frequently with Test Optimization..
Easy integration for Ant and Maven
With simple integration for Ant, Maven 1 and Maven 2, Clover Test Optimization can be added to any set of unit, functional or acceptance tests.
Improve your continuous integration process
With Test Optimization, you can significantly increase the number of build and test cycles your continuous integration environment can get through on a daily or weekly basis. Optimised builds not only help individual developers get quick feedback, they can also increase the velocity of your entire team.
FAIL faster, commit with confidence
Running the optimal subset of tests with each build takes the waiting out of testing. Clover automatically reorders your tests ensuring the ones that matter are run first. That means when your test fails, it does so fast, giving you the feedback you need to address the issue quickly.
Running more frequent builds with optimised tests gives you greater confidence that your commit will not break the main build. Learn more about how Test Optimization works.