Follow the steps in this document to set up Clover's Test Optimization, which allows targeted testing of only the code which has changed since the last build.
These steps assume your build is Clover-enabled already (in particular it has a
with.clover task already set up and has a taskdef established for the Clover Ant tasks). You will have to complement this quick start guide with basic Clover configuration information.
These steps also assume that your build file is currently used for a CI (Continuous Integration) build and possibly for general builds (e.g. On a developer's own machine). Below, we describe how you can take that build file and add sections to bake in Test Optimization. Adding optional support for Test Optimization (switching it on/off), specifying whether test minimisation is performed and test reordering other than the default 'failfast' are advanced options which are covered elsewhere.
Clover's Test Optimization feature currently do not support optimization for test cases written in Groovy (CLOV-1152):
Try to ensure your unit tests do not have dependencies between them as this may cause optimized builds to fail more frequently than usual.
You will need to use this:
Choose a location for the test snapshot file that can survive clean builds. This location:
The default is not as good as manually deleting this directory each build, but it is workable if you only use
<clover-clean/>as, by default, it won't delete snapshots. Add a property for this, as in the following example:
Add a target to generate the test snapshot:
<batchtest> element of the
<junit/> task used to test your application, so that the filesets are wrapped in the
clover-optimized-testset element. See the following example:
This becomes the following:
Run the optimized build (this will typically be run by their CI plan). Assuming a "test" target (with appropriate dependencies so that the code is instrumented/compiled):
Please note that Ant's <junit>/<batchtest> collects the included resources from any number of nested resource collections and then generates a test class name for each resource that ends in .java or .class. It means that you cannot use <include name="**/*Test.groovy"/> because such files will be ignored. However, you can point to *.class files, for example:
Using the configuration above, Clover will optimize tests according to: