> -----Original Message----- > From: Mike Perham [mailto:[EMAIL PROTECTED] > Sent: mercredi 5 avril 2006 15:52 > To: Maven Developers List > Subject: RE: Feedback needed on clover aggregation feature I'd like to > implement... > > Wow, that sounds cool. We're already blown away by the aggregated report. > > On second thought, I think that feature, while nifty, is not high > priority. In fact I believe we would disable it if possible. A module's > unit tests should exercise its code as much as possible and not rely on > other modules to exercise it. That's where the Clover report is useful - > to point out coverage weaknesses in the unit tests and this feature would > mask those weaknesses somewhat.
Mike, you're very right when it comes to unit tests. However this is for functional tests. For unit test what already exist is sufficient as you mention. For example in Cargo I have lots of functional tests and those test exercise the code. It's fair to count these tests when we compute the global test coverage because functional tests are exercising code. Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 05, 2006 5:58 AM > To: 'Maven Developers List' > Subject: Feedback needed on clover aggregation feature I'd like to > implement... > > Hi, > > I've just realized that there's work to be done on the clover plugin if we > want it to support aggregated clover reports. By aggregated reports, I > mean getting a single report for all modules. Right now this is possible > but each module will only contribute coverage for its own code. I'd like > that coverage generated by a module on some other module's code also gets > counted. > > For this I'm planning to try implementing the following: > > * Modify clover:instrument so that the forked lifecycle extends till the > install phase > > * Create an internal clover mojo bound to the install phase that will > created a clovered version of the project's artifact as an attached > artifact (classifier = "clover"). > > * Handle the different type of packaging. For example for a WAR packaging, > add the clover jar to the attached clovered WAR, etc. > > * Modify the clover:instrumentInternal so that for any dependency > artifact, it looks for the clovered version in the repo and adds it > instead of the non-clovered version. > > As this is pretty involved I'd like to be sure this is the right thing to > do. > > Thanks for any feedback! > -Vincdent > > > > > > > __________________________________________________________________________ > _ > Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les > tarifs exceptionnels pour appeler la France et l'international. > Téléchargez sur http://fr.messenger.yahoo.com > > --------------------------------------------------------------------- > 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] ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
