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
<[email protected]> 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 [email protected]
www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
