Jacoco code coverage for integration tests (quarkusIntTest) using Gradle

[pongohaja]

Hi there,

Have anyone succeeded in setting up and running jacoco for integration test classes annotated @QuarkusIntegrationTest when using Gradle?
I have tried to apply what is written at https://quarkus.io/guides/tests-with-coverage#coverage-for-integration-tests, chapter 8.1.
However, the instruction is aimed at projects using maven, so I made several efforts using Stackoverflow, ChatGPT and Gemini to create an equivalent build.gradle file. I fail all the time.
Is there some person out there having a working example of a build.gradle file set up for using jacoco started with ./gradlew quarkusIntTest

[brianwyka]

I've tried this myself as well, and have been unsuccessful. Would be nice to have this added to the documentation.

[LunaticoCR]

I'm on the same boat. If I run the test annotated with @QuarkusIntegrationTest directly from IntelliJ it works, I see the service gets started, ports are opened, and the test is able to make a REST request to the service.
However, when I run from CLI with ./gradlew quarkusIntTest the test fails, but the service does get started and the ports are opened, but it looks like the test fails to realise the service is up and running so it blows up.

The test fails with this:

java.lang.RuntimeException: java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.throwBootFailureException(QuarkusIntegrationTestExtension.java:372)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.beforeEach(QuarkusIntegrationTestExtension.java:117)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details
	at io.quarkus.test.common.LauncherUtil.waitForCapturedListeningData(LauncherUtil.java:102)
	at io.quarkus.test.common.DefaultJarLauncher.start(DefaultJarLauncher.java:72)
	at io.quarkus.test.junit.IntegrationTestUtil.startLauncher(IntegrationTestUtil.java:195)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.doProcessStart(QuarkusIntegrationTestExtension.java:300)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.ensureStarted(QuarkusIntegrationTestExtension.java:169)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.beforeAll(QuarkusIntegrationTestExtension.java:130)
	... 1 more

However I do see server logs confirming the service is up:

{"timestamp":"2024-07-04T16:05:13.101+01:00","sequence":75,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus.grpc.runtime.GrpcServerRecorder","level":"INFO","message":"Started gRPC server on 0.0.0.0:9000 [TLS enabled: false]","threadName":"vert.x-eventloop-thread-0","threadId":23,"hostName":"dev-machine","processName":"quarkus-run.jar","processId":4799}
{"timestamp":"2024-07-04T16:05:13.136+01:00","sequence":76,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus","level":"INFO","message":"my-service 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.9.3) started in 0.963s. Listening on: http://0.0.0.0:8081","threadName":"main","threadId":1,"hostName":"dev-machine","processName":"quarkus-run.jar","processId":4799}
{"timestamp":"2024-07-04T16:05:13.136+01:00","sequence":77,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus","level":"INFO","message":"Profile prod activated. ","threadName":"main","threadId":1,"hostName":"dev-machine","processName":"quarkus-run.jar","processId":4799}
{"timestamp":"2024-07-04T16:05:13.136+01:00","sequence":78,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus","level":"INFO","message":"Installed features: [cdi, grpc-server, logging-json, micrometer, rest, rest-client, rest-client-jackson, rest-client-jsonb, rest-jackson, rest-jsonb, smallrye-context-propagation, vertx]","threadName":"main","threadId":1,"hostName":"dev-machine","processName":"quarkus-run.jar","processId":4799}

And I confirmed this by doing nmap localhost and verifying ports 8081 and 9000 where open.

Where you guys getting this same error?