mcpField
4
421-frameworks-quarkus-testing-unit-tests

421-frameworks-quarkus-testing-unit-tests

github.com/jabrenaTesting & quality456319 installsUpdated 1d ago
Repository

About 421-frameworks-quarkus-testing-unit-tests

A skill for improving unit testing in Quarkus, favoring JUnit 5 and Mockito unless CDI integration requires QuarkusTest. It covers mocking, HTTP resource tests, parameterized tests, and test-specific profiles.

Key features

  1. 01Use JUnit 5 and Mockito without booting Quarkus
  2. 02Replace CDI beans with InjectMock
  3. 03Use InjectSpy for partial mocks
  4. 04Test HTTP resources with REST Assured
  5. 05Parameterize tests with CSV or method sources
  6. 06Configure tests with QuarkusTestProfile

Use cases

  1. 01Reduce QuarkusTest use in fast unit tests
  2. 02Test services with Mockito
  3. 03Add profile-specific test configuration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests

After installing, type/421-frameworks-quarkus-testing-unit-testsin Claude Code to confirm it loaded.

Bundled filesreferences/421-frameworks-quarkus-testing-unit-tests.md

Details

From the project README

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.

  • MANDATORY: Run ./mvnw compile or mvn compile before applying any change
  • PREREQUISITE: Project must compile before applying 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
  • BEFORE APPLYING: Read the reference for detailed rules and examples

When to use this skill

  • Add or improve unit tests in a Quarkus project
  • Reduce slow @QuarkusTest usage with Mockito-first tests
  • Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests
  • Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource
  • Write fast pure unit tests for Quarkus services

Workflow

  1. Read reference and assess project context

Read references/421-frameworks-quarkus-testing-unit-tests.md and inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

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

  1. Apply framework-aligned changes

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

  1. 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/421-frameworks-quarkus-testing-unit-tests.md.

Comments

Markdown supported