Dan, I apologize for this very late reply. We are currently leveraging cobertura against a tapestry application using Jetty6 and HtmlUnit/Canoo Webtest. We have a slightly different approach is that we have a single project which produces a war and we run our tests during the "integration-test" phase of that project. We do not have a distinct module to do unit testing. I had to do some modifications to the cobertura plugin to get it to instrument the correct class and dump the settings during the report phase (since we're running in the same process). We also had to write our own "integration-test" plugin which runs jetty, adds the htmlunit classes under src/itest to the fileset to be run during testing, and other odds and ends.
I am not sure if my approach is "the best" or if you even still need information. Feel free to ping me if you would like me to elaborate on our approach. So far we've been fairly successful and getting what we need out of Maven 2, but I have found that the "integration-test" phase is largely neglected in maven functionality, unless you are testing a maven plugin. Best, DeFrance -----Original Message----- From: Dan Adams [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 03, 2006 3:58 PM To: Maven users list Subject: [m2] code coverage for multiple modules that use integration tests Okay, I have a number of modules and I want to generate code coverage for them with cobertura. Some of the classes can be tested with normal unit tests so they are not a problem. Some of the classes, however, are Tapestry components. To test them I have a separate module called integration-tests that runs a web app and uses html unit to test them. Anyone know of a way that I can have cobertura include the results from the integration tests when calculating coverage for the modules? -- Dan Adams Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- 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]
