An integration test evaluates an application with externally packaged or connected components. In Quarkus, the test JVM runs separately from the application artifact and exercises only its exposed API, unlike a same-JVM Quarkus test. section 2.2.2
A practical integration-test flow:
- Annotate a test with @QuarkusIntegrationTest to run it against packaged application artifacts. section 2.2.2
- Reuse endpoint assertions from a @QuarkusTest class when the same behavior applies in both execution modes. section 2.2.2
- Exercise REST endpoints with REST Assured and verify status codes and response bodies. section 2.2.2
- For messaging, inject KafkaCompanion, stub unavailable REST clients, invoke the API, and verify that the expected Kafka message was produced. section 9.6.2
Verifying a Kafka invoice adjustment
A rental-service test mocks the ReservationClient, starts and ends a rental through REST, then listens on the invoices-adjust Kafka topic to confirm that the prolonged rental produced an invoice-adjustment message. section 9.6.2
Listing 2.6 Quarkus integration test
package org.acme;
import io.quarkus.test.junit.QuarkusIntegrationTest;
@QuarkusIntegrationTest
public class GreetingResourceIT extends GreetingResourceTest {
// Execute the same tests but in packaged mode.
}
Inspect the packaged-mode test that inherits the endpoint checks and runs them against the built application. section 2.2.2
