Code Coverage Jacoco

[cprouveu]

Hello,

I use Jacoco for code coverage report and I don't know since which release the report don't work anymore.
Report get only classes in tests files, not in other files while test execution.
I'm using keycloak 26.1.4.

Do you know if a config is needed ?

Thanks

[bernhof]

Mostly, this sample repo helped us set things up to measure coverage with Jacoco. However, we're seeing that certain classes are not covered. Is this what you're seeing, too @cprouveu?

A different version of class was executed at runtime.

There's no clear reason why (ie. we're doing no post processing of class files) but Jacoco docs indicate that this is due to class bytecode changes at runtime (in the container).

Quarkus may be doing some post processing of the classes, but I'm unsure how to work around this. Maybe https://quarkus.io/extensions/io.quarkus/quarkus-jacoco/ could help in combination with https://github.com/mabartos/keycloak-quarkus-extensions (to apply Quarkus extenions) but it's just a guess at this point.

@dasniko: Do you have any pointers that could help?

[cprouveu]

Yes, it's still there.

I think it's link with the warning :

[WARNING] Classes in bundle 'keycloak' do not match with execution data. For report generation the same class files must be used as at runtime.
Some forum says it's a mismatch version of java in main and depency build.

I'm still searching.

[cprouveu]

@bernhof
I found testContainer is build in java 17 and container using java 21.
Maybe it's the cause.

@dasniko
Is it possible to change test container to use java 21 as Java 17 support is deprecated since 25.0.0 ?

[dasniko]

This library is used by countless other projects, even those which still requires Java 11 support. Therefore, although this library's code is implemented with Java 17, it is built with version 11 level!
It's not always as easy as it seems at first sight. And Jacoco support is not on my feature list, sorry.

[dasniko]

I don't know Jacoco, sorry.