Re: Measuring integration test code coverage for a Maven plugin

2007-12-10 Thread Dan Fabulich
Raphaël Piéroni wrote: My guess is that you should deploy your instrumented plugin in a test repository. That's basically what I wound up doing. For the record, I started by specifying a special local repository in my setting directory. Then I tried just using maven-clover-plugin 3.6, call

Re: Measuring integration test code coverage for a Maven plugin

2007-12-09 Thread Raphaël Piéroni
Hi, I never yet seen such thing. But i would be very interested in the answer. My guess is that you should deploy your instrumented plugin in a test repository. Regards Raphaël 2007/12/7, Dan Fabulich <[EMAIL PROTECTED]>: > > I recently added a bunch of integration tests for Surefire. These >

Measuring integration test code coverage for a Maven plugin

2007-12-06 Thread Dan Fabulich
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? Specifical