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?
Clover has over two dozens of properties, which you can pass to JVM during compilation, runtime or reporting:
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:
There are few settings used by Clover-for-Ant during compilation:
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.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot