I recently added a bunch of integration tests for Surefire. These integration tests automatically fork a separate Maven process to run real Maven builds, like the Maven core integration tests do.
This naturally led me to wonder: Does Surefire (now) have reasonable code coverage? Specifically, which lines in Surefire were covered by unit tests, which by integration tests, and which weren't covered at all?
I know there's a variety of handy code coverage tools that work with Maven, allowing you to instrument classes for code coverage and run your unit tests against the instrumented classes.
The catch in this case is that I need to somehow convince Maven to use the instrumented version of my plugin, and not the regular "real" version of the plugin, when I go to run my integration tests. The clover plugin, for example, doesn't seem to want to let me do that.
[On the other hand, maybe I should just use an instrumenting JVM instead...? Java 1.5's new java.lang.instrument would probably do the trick, but I'm not aware of any code coverage tool that works with j.l.instrument, and anyway I'd have to fix SUREFIRE-179 just to get it to work... :-)]
Has anybody ever done this before? More generally, I don't think I've ever seen an example of anyone using Maven to run multi-process integration tests (e.g. cargo tests) and also measuring code coverage on those integration tests. Has anyone seen a good example of this that I could reuse?
-Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
