Quarkus Unit Testing

Apply fast testing strategies for Quarkus: Mockito-first, QuarkusTest when CDI wiring matters.

What is covered in this Skill?

• Pure JUnit 5 + Mockito without container boot (@ExtendWith(MockitoExtension.class))
• @QuarkusTest with @InjectMock for full CDI bean replacement
• @InjectSpy for partial mocking — real bean wrapped as spy, specific methods overridden
• REST Assured for HTTP-level @QuarkusTest resource tests
• @ParameterizedTest with @CsvSource (inline data) and @MethodSource (complex objects)
• QuarkusTestProfile and @TestProfile for test-specific configuration overrides
• Naming conventions: *Test → Surefire (fast phase), *IT → Failsafe (verify phase)
• When to escalate to integration tests (@422)

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

Constraints

Compile before test refactors; verify the full suite after.