> -----Original Message----- > From: Nelson Carpentier [mailto:[EMAIL PROTECTED] > Sent: vendredi 4 août 2006 02:47 > To: [email protected] > Subject: Maven Philosophy...
[snip] > 2) Coverage. Not only do we want to know what our "unit test" coverages > are, > we want to know what our end-to-end coverage is. For us, end-to-end > numbers > include harnessing data on coverage from "unit testing" *and* "integration > tests", which others may feel more comfortable calling "application > tests". > (For us, "integration tests" = actually deploying the app,and hitting it > with HTMLUnit, etc...) > I don't see how we can get these numbers for a n-tier project within the > standard Maven multi-module build, and/or with using the Cobertura plugin. FWIW this is currently supported in the Clover plugin. The plugin does this by creating clovered artifacts that it installs in your local repository and swaps a project's dependencies in favor of those clovered one when it finds them. I'm using it on Cargo's build successfully to report on full project coverage. -Vincent ___________________________________________________________________________ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
