422-frameworks-quarkus-testing-integration-tests
This Claude Code skill provides guidance for writing and improving integration tests in Quarkus projects, covering @QuarkusTest for in-JVM testing with real CDI wiring, Dev Services and Testcontainers for automatic container provisioning, WireMock for HTTP mocking, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured for HTTP assertions, and data isolation strategies using @TestTransaction and Maven Surefire/Failsafe splits. Use it when adding or refactoring integration tests, configuring test infrastructure with containers, stubbing external dependencies, or fixing test data isolation issues in Quarkus applications.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/422-frameworks-quarkus-testing-integration-tests && cp -r /tmp/422-frameworks-quarkus-testing-integration-tests/skills/422-frameworks-quarkus-testing-integration-tests ~/.claude/skills/422-frameworks-quarkus-testing-integration-testsSKILL.md
# 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).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project