Hello Marc,
Here is my description of the approach.
-
Add the option to choose a mode of JaCoCo run. This option could be
handled by a system property named e.g. org.jacoco.source.detection.enabled
with possible values true or false configured in the maven pom file.
Default value should be false and JaCoCo execution will be the same as
before.
-
Identify test calling source code.
-
We can get this data from actual stack trace when code was visited in
a coverage counters spots (places analyzed by JaCoCo). An extension of
the
ClassProbeAdapter and changes in org.jacoco.core.internal are needed.
-
Verify new functionality for all analytical methods.
-
Data storing
-
Implementation of storing extension in package org.jacoco.data.core.
We need to store data about from where was code called. Saving should be
fast and duplicities of calls should be ignored.
-
Display data
-
Extend actual report with data about source calling (changes in
org.jacoco.report package),
-
Data merge - in the jacoco report we can see coverage from package to
code. For a package it would be nice to display all tests. So I would
like
to show what tests cover each particular package.
Best regards
Jakub
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/77d84d54-62ef-45df-94d1-ffff057f033c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
