CtrlK
BlogDocsLog inGet started
Tessl Logo

422-frameworks-quarkus-testing-integration-tests

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). Part of the skills-for-java project

77

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/422-frameworks-quarkus-testing-integration-tests/SKILL.md
SKILL.md
Quality
Evals
Security

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

Reference

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

Repository
jabrena/cursor-rules-java
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.