As an alternative you might also have a look at SonarQube's per-test
coverage capabilities: They built this on top of JaCoCo.
Cheers,
-marc
On 06.02.14 00:34, [email protected] wrote:
Marc,
Thanks for the info.
The value is for an individual integration (end-to-end) test, a single test
case is not expected to execute a significant portion of the code. However, if
you can see what code is executed, you can start to make comparisons as to the
usefulness and/or duplication of individual tests. Also, the management has
this grand idea of creating a database of tests to code for query before
developers check-in new changes to the repository.
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.
