That's correct, depending on how you are invoking the cobertura, you will see that. Basically the "cobertura" goal is going to invoke a parallel lifecycle that will run the test. It is easy to modify the plugin to do what you want, if you don't then someone has done it for you:
http://top.touk.pl/maven2/release/org/codehaus/mojo/cobertura-maven-plugin/2.2-touk That's a m2 repo. It has one additional goal "generate-report" that will *not* fork a lifecycle, so you won't have the hudson double or treble vision. (There is no doc. on the plugin, but basically you clean,instrument, generate-report in different phases of your regular build). Thanks, mohan kr -----Original Message----- From: David C. Hicks [mailto:[email protected]] Sent: Monday, July 20, 2009 8:51 PM To: Maven Users List Subject: Re: Surefire/Cobertura roll-up reports? Adam Purkiss wrote: > As for surefire - no idea, but using Hudson as our CI tool I have it setup to > "roll up" the Junit results to a top level using its reporting. > We use Hudson, as well, but we've noticed that between Surefire and Cobertura, we end up with two or three "copies" of each test result. So, it appears like we have 2 to 3 times more unit tests than we really do. I guess it depends on what Hudson is rolling up. Perhaps I'm using the plugins in a way that I should not be. I'm trying to satisfy both the needs of the development team in getting code built and deployed to a test server (where we then come back and run some automated integration tests through Maven with Selenium) and the desires of management who really love to look at the pretty reports. :-) It was actually this discrepancy in the Hudson rollup that prompted my question in the first place. Otherwise, that's a great suggestion. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
