Closing the Gap: Test Coverage for Quarkus Extensions

[giscus[bot]]

Closing the Gap: Test Coverage for Quarkus Extensions

Quarkus: Supersonic Subatomic Java

https://quarkus.io/blog/quarkus-test-coverage-extensions/

[hamburml]

I am curious - afaik quarkus-jacoco only works with QuarkusTest annotation. When I have plain unit tests it does not report the coverage of these. Is this also the case when using it in extensions?

[cescoffier]

/CC @mkouba

[mkouba]

I am curious - afaik quarkus-jacoco only works with QuarkusTest annotation. When I have plain unit tests it does not report the coverage of these. Is this also the case when using it in extensions?

@hamburml For plain unit tests you need to configure the jacoco-maven-plugin; the docs descibe a case where at least one @QuarkusTest is run in the test suite.

[hamburml]

@mkouba Thanks. I know it is a different scope but: We discussed this in my work group, and most people don’t want to mix the plugin with the dependency, since we’re using both unit tests and Quarkus tests depending on the scope of the maven module. They want a single configuration that covers both, copy the pom.xml to a newly created maven module or project. So the majority is leaning toward using only the JaCoCo plugin and skipping the dependency. Personally, I’d prefer the dependency approach if it can handle both as well. Thanks for answering :)

[mkouba]

They want a single configuration that covers both, copy the pom.xml to a newly created maven module or project. So the majority is leaning toward using only the JaCoCo plugin and skipping the dependency.

This won't work. If you combine @QuarkusTest and plain unit tests you will need both - quarkus-jacoco extension for @QuarkusTest and jacoco-maven-plugin for plain unit tests.