Definitely depends on your definitions for integration test and circumstances. We run our Spring context-based and other long-running tests via a special profile-activated surefire configuration together with plain unit tests to get accurate code coverage counts.
Kalle On Wed, Jan 27, 2010 at 11:22 AM, Roland Asmann <roland.asm...@adesso.at> wrote: > Depends on what you call 'integration test'... If it's a couple of tests > inside a single module, just use cobertura/clover/something else... > > If you want an integration-test of several modules, try something like this > (working on it myself, not finished, so no guarantees!): > -- (the maven-invoker-plugin springs to mind for this) > - trigger a new life-cycle for the modules you need, using a profile that > packages the modules WITH the cobertura/clover/other classes, so the tests > will be run with coverage-classes > - have this life-cycle use a separate repository > - run all your tests using the artifacts from aforementioned repository > - have the cobertura/clover/other report the findings for you > > As I said, for me it's still a work-in-progress (although I've build 2 > projects in a similar fashion, but I wasn't quite satisfied by the number of > manual steps still involved), but it's a start... > > > On 27-01-10 18:44, Wendy Smoak wrote: >> >> On Wed, Jan 27, 2010 at 10:07 AM, Douglas Ferguson >> <doug...@douglasferguson.us> wrote: >> >>> Is there anyway to get code coverage numbers for integration tests? >> >> I'm sure it's technically possible, but as far as I know, no one has >> done it yet with Maven. It's definitely on my list of things I'd like >> to see! Let us know if you figure it out. :) >> > > -- > Roland Asmann > Senior Software Engineer > > adesso Austria Service GmbH > Bäckerstrasse 1/2/7 T +43 1 5138877-27 > A-1010 Wien F +43 1 5138862 > E roland.asm...@adesso.at > www.adesso.at > > ------------------------------------------------------------- > >>> business. people. technology. <<< > ------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
