It seems that the flushinterval directive is not working with clover 3.1.4. When I run the instrumented code in a JVM nothing is writting to the recordings files until the jvm is shutdown. Here's the clover-setup I'm using in ant to instrument the code.
<clover-setup initstring="/opt/tomcat/temp/clover/clover.db" instrumentationLevel="statement" flushpolicy="interval" flushinterval="1000" />
Once I start the JVM it creates a file named clover.db.liverec in the same directory as my clover.db file however no coverage data is written until the JVM shuts down.
I've also tried flushpolicy="threaded" with the same results.
In my case, I don't get code coverage even after I shut down Tomcat... Tried with Interval at 5000. Even my liverec file does not go away after I shut down tomcat.. Please help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.