How to debug QuarkusIntegrationTest in IntelliJ ?

[kirankolli-addepar]

When I add breakpoints on application code and then run my Quarkus Integration Test ( via quarkusIntTest gradle task) the code execution never pauses on the breakpoints.
Any solutions to this ?

Quarkus version = 2.9.2Final
IntelliJ version = IntelliJ Ultimate 2023

[quarkus-bot[bot]]

/cc @geoand (testing)

[geoand]

Assuming you are testing a jar, you can set quarkus.test.arg-line=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005

[kirankolli-addepar]

do you mean override quarkus.test.arg-line property by passing a VM args via -Dquarkus.test.arg-line=... ? If yes, that did not work.

[kirankolli-addepar]

to clarify the command used to run the test by IntelliJ is this :
gradle quarkusIntTest --tests "<Class name>" -Dquarkus.test.arg-line=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005' and this did not work

[kirankolli-addepar]

Next update on the answer :

Add a system property using the values as mentioned like so :

Also create a remote debug config for your application on IntelliJ to connect on localhost:5005 like so :

If your integration test used RestAssured to test a rest endpoint make sure to increase the timeout ( see here: rest-assured/rest-assured#1444)
Then start your gradle quarkusIntTest task and then also start your remote debugging session and this should work.

I wish it was easier than this though.

[maxandersen]

Tip is to set suspend=y so it Will wait for Connect.

Also using "Attach" from intellij or eclipse removes need to setup the debug config.

[kirankolli-addepar]

Are you suggesting to start the test as so ?

If yes, this option does not work. The test fails with the above setup.

And without quarkus.test.arg-line it never stops at the breakpoints. Usually I had never had to deep dive so much just to debug with other frameworks. With quarkus its unusually hard and totally not dev friendly which is the USP of quarkus being touted around.

[geoand]

Using quarkus.test.arg-line=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005 in application.properties does work when you run mvn verify. The integration test waits until you attach a debugger

[kirankolli-addepar]

but this still requires a separate debugger to be attached which is not a good developer experience at all.

[geoand]

Indeed. I suggest opening an issue on Jetbrains issue tracker

[kirankolli-addepar]

isnt this a quarkus problem though? the way integration tests have been implemented necessitates this.

[geoand]

It is intended that QuarkusIntegrationTest launches a separate JVM, it's not a problem/bug.

[kirankolli-addepar]

Yep tried this too, but it didnt work.

[ennishol]

I tried to put quarkus.test.arg-line=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:50 into application.properties and ran mvn verify and it did work. I could debug it by attaching to process with IDE