3 ms·

Have you come across JaCoCo [1]? It does its instrumentation via a JVM agent at runtime-- no need to recompile your code just to test for coverage. I've been u

Have you come across JaCoCo [1]? It does its instrumentation via a JVM agent at runtime-- no need to recompile your code just to test for coverage. I've been using it for the last year or two and love it! One of my favorite features is how easy it is to generate separate coverage information for unit tests vs. integration tests. Sonar provides excellent support for it, as well. [1] http://www.eclemma.org/jacoco/trunk/doc/ http://www.eclemma.org/jacoco/trunk/doc/

yoava 13y ago
It is a great tool, and I have used it. I have also used Emma. Both use instrumentation at loading time, which is great (because it is transparent). However, both recommend to run tests twice because of the instrumentation. In both cases, the Maven plugin runs tests twice - once for testing, and once for coverage - which is a total waist of time. I was thinking on using the debug interface to track coverage without instrumentation, those without the risk of modifying the tests.