422 Frameworks Quarkus Testing Integration Tests

---
name: 422-frameworks-quarkus-testing-integration-tests
description: Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# 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

## When to use this skill

- Add or improve integration tests in a Quarkus project
- Configure Testcontainers or Dev Services for Quarkus tests
- Add WireMock stubs for external HTTP dependencies in Quarkus integration tests
- Set up @QuarkusIntegrationTest for packaged artifact or native binary testing
- Fix test data isolation or configure Maven Surefire/Failsafe split

## Workflow

1. **Read reference and assess project context**

Read `references/422-frameworks-quarkus-testing-integration-tests.md` and inspect the current project setup before proposing changes.

2. **Gather scope and decide target improvements**

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

3. **Apply framework-aligned changes**

Implement or refactor configuration/code following the reference patterns and project conventions.

4. **Run verification and report results**

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

## Reference

For detailed guidance, examples, and constraints, see [references/422-frameworks-quarkus-testing-integration-tests.md](references/422-frameworks-quarkus-testing-integration-tests.md).