How do I install the 421 Frameworks Quarkus Testing Unit Tests skill?

Run npx skillmds add majiayu000/421-frameworks-quarkus-testing-unit-tests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 421 Frameworks Quarkus Testing Unit Tests safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 421 Frameworks Quarkus Testing Unit Tests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 421 Frameworks Quarkus Testing Unit Tests free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 421 Frameworks Quarkus Testing Unit Tests?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

421 Frameworks Quarkus Testing Unit Tests by majiayu000

Name: 421 Frameworks Quarkus Testing Unit Tests
Rating: 4.2 (5 reviews)
Author: majiayu000

421 Frameworks Quarkus Testing Unit Tests

Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as 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. Part of cursor-rules-java project

majiayu000 ec8cc2b 2 files · 4.3 KB Updated Sep 9, 2026 567 repo stars

File contents

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

Workflow

Read reference and assess project context

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

Gather scope and decide target improvements

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

Apply framework-aligned changes

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

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.

---name: 421-frameworks-quarkus-testing-unit-testsdescription: Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as 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. Part of cursor-rules-java projectlicense: Apache-2.0---# 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 ## 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. 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/421-frameworks-quarkus-testing-unit-tests.md](references/421-frameworks-quarkus-testing-unit-tests.md).

Frequently asked questions