Hi Martin,

first of all: This is not possible out-of-the box with JaCoCo tools.

Using the JaCoCo core APIs you can filter on those classes where execution data was actually recorded for (i.e. execution data is contained in the respective exec file).

I wonder what the value of the created coverage report actually is: This way you strip-off those classes from the report which have *not* been tested. So you can't see what classes you actually missed by the tests.

Cheers,
-marc


On 2014-02-04 20:56, [email protected] wrote:
I have a fairly large application that we'd like to get coverage
reports for each individual integration test. The idea is to give devs
a list of integration tests required for their code modifications.

I can (and have) create the .exec output files for each test invoked
on the system, but the report generate is huge. The HTML directory is
>100 MB and the XML output is ~50MB. Most of the application isn't tested by a 
single test, so the counts are 0. Considering the number of tests we'd eventually 
like to cover (multiple 1000s), we're looking at multiple terabytes for a single 
run.

What I'd like to do is have 1 combined report for total test coverage,
and then for each individual test limit the output to only those
classes actually executed. I know this is going to take multiple
passes over the .exec files. Is this possible to do via a combination
rules and reports, etc?

Thanks,
Martin

--
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/groups/opt_out.

Reply via email to