Including external (e.g. library) code as part of the coverage

[Pierre-Charles David]

Hi,

I'm trying to implement the following scenario, but I'm not sure if it is supported and if so, how to do it:

1. I have a "base" app, which provide a basic set of features. It is built and packaged in its own project, with the resulting JARs published on a Maven repo.
2. I also have a second "extended" app, which reuses "base", but adds more features, and wraps/extends some of the features from "base".

Both apps have their own tests, and both use JaCoCo for code coverage.

My issue is that when running tests and code coverage on "extended", only the code which is actually defined in "extended" is considered in the coverage computation. I'd also like JaCoCo to instrument the code from "base" and include that in the report so that I know which parts of "base" or not exercised/tested when running "extended".

Another similar scenario which may be simpler to understand if my explanation is confusing: imagine someone has published a library "lib" on Maven central, which I don't control. I want to write my own project "lib-tests" which depends on "lib" and includes tests to check lib's behavior in some specific settings. How can I configure JaCoCo in "lib-tests" to tell me how much of "lib"'s code I'm covering and what I'm missing?

Thanks.