How to reconfigure Clover at runtime or make performance tuning?

[Marek Parfianowicz]

Let's assume that I have instrumented and compiled code using Clover with some settings (such as initstring, flush policy etc). Is there any way to change these settings at runtime when running tests? Are there any means to speed up Clover during compilation or runtime, especially for large applications?

[Marek Parfianowicz · Accepted solution]

Clover has over two dozens of properties, which you can pass to JVM during compilation, runtime or reporting:

• https://confluence.atlassian.com/display/CLOVER/JVM+properties

Thanks to them, you can override Clover's default settings or settings which were configured in a build file.

Some of the settings worth noticing:

• clover.enable, clover.profile, clover.pertest.coverage, clover.pertest.coverage.threading - enabling and configuring Clover's coverage recorders
• clover.server, clover.distributed.coverage - configuring distributed coverage feature
• clover.initstring, clover.initstring.basedir, clover.initstring.prefix - changing location in which Clover looks for a database file

There are few settings used by Clover-for-Ant during compilation:

• clover.includes, clover.excludes

Similarly, the Clover-for-Maven plug-in has a number of configuration options which can be also passed as -Dkey=value parameter for Maven, for instance:

• maven.clover.flushPolicy, maven.clover.jdk, maven.clover.cloverDatabase

There is also a possibility to tune Clover's performance during compilation and reporting - see https://confluence.atlassian.com/display/CLOVER/Clover+Performance+Tuning.