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; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with strong validation checkpoints and clean progressive disclosure to a single reference. Its main weakness is actionability: the body itself carries no executable testing examples, leaning entirely on the reference for the concrete guidance.

Suggestions

Include 1-2 minimal executable snippets in the body (e.g., a MockitoExtension pure test and an @QuarkusTest + @InjectMock skeleton) so the skill is actionable without opening the reference.

Tighten step 3 of the Workflow from 'Implement or refactor following the reference patterns' to name the specific patterns to apply per scenario (Mockito-first vs @QuarkusTest vs @ParameterizedTest).

Make the @422 escalation trigger explicit in the body (currently only the description mentions it) so the 'when to escalate to integration tests' bullet is actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every section earns its place and it assumes Claude's competence.	3 / 3
Actionability	Constraints give concrete commands (mvnw compile, mvnw clean verify) but the core testing guidance is abstract ('Implement or refactor configuration/code following the reference patterns') with no executable code or examples in the body, deferring all specifics to the reference — the 'some concrete guidance but incomplete' anchor fits.	2 / 3
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-on-failure, VERIFY after) provides the feedback loop the rubric rewards.	3 / 3
Progressive Disclosure	A concise overview points to a single real, correctly-linked one-level-deep reference (references/421-frameworks-quarkus-testing-unit-tests.md, which exists on disk); navigation is easy and content is appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly states capabilities and use-conditions and disambiguates from sibling skills. No first/second-person voice issues. Could only be trimmed slightly for length, but verbosity is not penalized enough to lower a score.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities (@ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock, @InjectSpy, REST Assured, @ParameterizedTest with @CsvSource/@MethodSource, QuarkusTestProfile, Test/IT naming), matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	It answers both what (the enumerated testing approaches) and when via an explicit 'Use when...' opening and a 'This should trigger for requests such as...' list, satisfying the top anchor.	3 / 3
Trigger Term Quality	Natural trigger phrases users would say are explicitly given ('Add or improve unit tests in a Quarkus project', 'Reduce slow @QuarkusTest usage with Mockito-first tests', 'Convert repeated test methods to @ParameterizedTest'), giving good coverage of real-world phrasings.	3 / 3
Distinctiveness Conflict Risk	It carves a clear Quarkus-specific niche and explicitly redirects framework-agnostic Java to @131-java-testing-unit-testing, minimizing wrong-skill triggering.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Commit: aaee915

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.