Hi,
we have to separate two things:
1) Execution data sampling during test execution: The JaCoCo agent
samples execution data for all classes loaded into the JVM, therefore
also classes from the dependencies.
2) Coverage report generation: Our Maven report goal only considers the
classes from a single module -- here is the actual limitation for multi
module tests.
Especially PR #195 tries to address issue 1) which is actually not the
point.
Currently there are at least two workarounds:
1) Create the report with the report Ant task. The JaCoCo build itself
does it this way.
2) Use SonarQube for reporting which can deal with multiple reports.
Best regards,
-marc
On 17.05.14 19:32, [email protected] wrote:
Hi,
I read about issue #195 and #97 but both of these haven't been merged in the
master (closed and pull not accepted).
So I deduced that it is always not possible to have Itests covered lines for
submodules?
For example, let's have a project made with two modules, my.biz and my.data:
my.biz having my.data as dependency.
It's allgood for me that test coverage on my.biz covers only classes from the
my.biz module, but for INTEGRATION tests, coverage on my.biz should covers
classes from my.biz AND my.data (all solutions I tried from now ended with only
my.biz covered classes report).
Is it possible to do this? How? Have you got a pointer?
Thank you in advance.
Regards,
--
You received this message because you are subscribed to the Google Groups "JaCoCo
and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
