Application startup problems when running tests via the @QuarkusTest annotation

[poker303]

Describe the bug
Reservation: I'm not sure if this's a bug or a work limitation of the annotation @QuarkusTest. This is our first big project on this framework, so please don't judge strictly.

My team and I write a project on Kotlin, using Quarkus as the main framework, and Gradle as the main build system. We have an application that we are currently covering with tests. The problem arises when we write REST-http tests to our EndPoints. The tests work out correctly, but only when we run them, with the application running. But if we turn off the application and put the @QuakusTest annotation, which, according to the documentation, should run the application itself before running the tests, an exception occurs:

"Connection refused: no further information
java.net.ConnectException: Connection refused: no further information"

Although the application itself is running.
We think that the problem may arise from working with GraphQL Schema.

We understand that requests should be sent to http://localhost:8081/mapins but it doesn't work. We get such response: "GraphQL Schema not generated. Make sure you have a GraphQL Endpoint. Go to https://quarkus.io/guides/microprofile-graphql to learn how". When we exclude the path from requests for autoconfiguration we get the same result as in the case when we send requests to http://localhost:8081/ - responses are just empty. We have already tried using quarkus.http.test-port but result are the same... Maybe the problem is that our application is multimodule and needed to be started from concrete module and @QuarkusTest uses some kind of default command?

This is a link (https://github.com/Bazalii/Interactive-map) to our small test project on github, on which we tested the work of a real project.

Output of java -version
Java 17, Kotlin 1.6.21

Quarkus version or git rev
2.11.1.Final

Build tool (ie. output of mvnw --version or gradlew --version)
Gradle 7.4.2

Additional information
We searched Internet for information about this problem, but the only thing we found was a bit similar question on StackOverflow, where the solution was - to connect "io.quarkus:quarkus-resteasy-reactive-jackson". We tried this option, but it didn't help(

Our tests:

Application properties:

Error when trying to run tests without an enabled application on a standard port:

Error when trying to run tests without the application enabled on port 8080:

Tests when the web application is running from the module:

[quarkus-bot[bot]]

/cc @evanchooly, @geoand

[geoand]

Hi,

Isn't this a duplicate of #28448?

[Bazalii]

Hi!

Yes, but right now it's placed in correct topic because you said that it's not the issue with quarkus but our problem. Unfortunately, we didn't get wanted answer there except proposal to read articles and check projects which we've already seen and processed. So, we decided to put it here because it seems to me that answers here are more meaningful and maybe someone else would help us with our problem.

Sorry for tagging again, didn't thought that area is bound to tagging same people here.

[geoand]

No need to apologize, just asking to make sure we are on the same page :)

[geoand]

To reiterate, I'll just say that @QuarkusTest always starts the Quarkus application and also configured RestAssured with the base URL of the application.

@Sgitario is there anything more you would like to add here?

[Bazalii]

./gradlew clean test

They do fail but for a different reason, something about uuid not matching.

The problem with UUID is that we get such response and not the correct one:

[aloubyansky]

./gradlew clean test
They do fail but for a different reason, something about uuid not matching.

The problem is still the same. Application for tests is not active and as a result we get as a response 404 and not 200 as expected:

MapControllerHttpTests > getAllWalls_SuccessPath_AllWallsFoundAndCorrectStatusCodeIsReturned() FAILED java.lang.AssertionError at MapControllerHttpTests.kt:30

It means the URL does not respond with the expected code/content but it's not because the app wasn't bootstrapped. You can see in the logs the app did start w/o errors.

The next fix would be to add META-INF/beans.xml to the web subproject (the same way it is added to the core).

[Bazalii]

@aloubyansky adding META-INF/beans.xml to the web worked for me! Thank you very much!

[aloubyansky]

@Bazalii here is what you need to know about the @QuarkusTest to get this cleared, @QuarkusTest will use the module (or subproject in Gradle's terms) the test belongs to as the main application's module. In your case, the web subproject is not the main module of the application you are testing, it's a dependency of the test application. As a consequence, to make the beans and other stuff available in your test application, you need to add META-INF/beans.xml to the web subproject.

[Bazalii]

@Bazalii here is what you need to know about the @QuarkusTest to get this cleared, @QuarkusTest will use the module (or subproject in Gradle's terms) the test belongs to as the main application's module. In your case, the web subproject is not the main module of the application you are testing, it's a dependency of the test application. As a consequence, to make the beans and other stuff available in your test application, you need to add META-INF/beans.xml to the web subproject.

Okay, thank you for explanations and for your attentive help with this problem! It cannot be described in words for how long we have tried to solve the problem and the solution was just so simple..