Quarkus Integration Testing

Apply integration testing patterns for Quarkus with real wiring and reproducible infrastructure.

What is covered in this Skill?

@QuarkusTest for in-JVM integration with real CDI wiring
Dev Services for automatic container provisioning (%test.quarkus.datasource.devservices)
Testcontainers via QuarkusTestResourceLifecycleManager (start/stop lifecycle, dynamic config injection)
WireMock for stubbing external HTTP services via QuarkusTestResourceLifecycleManager
@QuarkusIntegrationTest for black-box testing against the packaged JAR or native binary
HTTP testing with REST Assured against the Quarkus test port
Data isolation: @TestTransaction for automatic rollback; @BeforeEach cleanup for HTTP tests
Maven three-tier split: *Test → Surefire (fast), *IT + *AT → Failsafe (verify)
Native-image test considerations with @DisabledOnNativeImage

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Compile before changes; verify after; Docker may be required for containers.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
PREREQUISITE: Project must compile before applying integration test improvements
SAFETY: If compilation fails, stop immediately
BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements; Docker is required for Testcontainers and Dev Services
BEFORE APPLYING: Read the reference for detailed rules and examples