This is the documentation for Clover 3.3. View this page for the

Unknown macro: {spacejump}

of Clover, or visit the latest Clover documentation.

Q: Why do I get 0% coverage when I run my tests and then a reporter from the same instance of Ant?

This occurs because Clover hasn't had a chance to flush coverage data out to disk. By default Clover flushes coverage data only at JVM shutdown or when explicitly directed to (using an inline directive). The simplest thing to do is to use the {{fork="true"}}attribute when running your tests. The tests will then be run in their own JVM, and the coverage data will be flushed when that JVM exits. Alternatively, you can use interval-based flushing by changing the Flush Policy.

  • No labels





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.