Test Optimization
In the new Test Optimization feature, Clover now has the ability to optimise test runs, which greatly reduces the time taken to test a code change. Traditionally, the full suite of tests is run whenever a small code change is made. Now, for a given edit, Clover works out the optimal subset of tests that will exercise that change. Running the optimal subset is in general dramatically faster than running the full test suite. This means that developers are more likely to run tests prior to committing, and Continuous Integration servers can get through far more build and test cycles. This means faster feedback to developers when their code changes break tests.
Read more: Ant, Maven2
|