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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured, lean overview with clear validation checkpoints and clean one-level-deep reference navigation. The main weaknesses are redundant compile-first restatements and the deferral of all executable code examples to the reference file.

Suggestions

Collapse the four near-duplicate compile-first bullets in Constraints into a single clear rule (e.g., 'MANDATORY: run ./mvnw compile before any change; stop and have the user resolve errors if it fails').

Drop or compress the 'When to use this skill' section since it duplicates the frontmatter description's triggers verbatim.

Add one small inline example per core technique (e.g., a minimal @QuarkusTest + @InjectMock snippet) so the body is actionable without requiring a round-trip to the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the Constraints section restates the compile-first rule across four near-duplicate bullets (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION) and 'When to use this skill' repeats the description's triggers verbatim, so it could be tightened.	2 / 3
Actionability	Concrete commands (./mvnw compile, mvn clean verify) and named annotations are present, but the body defers all executable test code and good/bad examples to the reference file, leaving the inline guidance incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	A numbered four-step workflow is paired with explicit validation checkpoints (compile before changes, stop immediately on failure, run clean verify after), providing a clear sequence with a compile->stop->verify feedback loop for error recovery.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing to a single one-level-deep reference (references/421-frameworks-quarkus-testing-unit-tests.md, which exists on disk), clearly signaled in both the workflow and a dedicated Reference section, with content appropriately split between overview and detail.	3 / 3
	Total	10 / 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 scopes the skill to Quarkus unit testing and disambiguates from the framework-agnostic sibling. Both the what and when are explicit, with natural trigger phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and techniques (pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock, @InjectSpy, REST Assured, @ParameterizedTest with @CsvSource/@MethodSource, QuarkusTestProfile, Test/IT naming), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (write fast unit tests for Quarkus via the listed approaches) and when ('Use when you need to write fast unit tests for Quarkus applications' plus 'This should trigger for requests such as...'), matching the clear what-and-when anchor.	3 / 3
Trigger Term Quality	Includes natural user phrasings such as 'Add or improve unit tests in a Quarkus project', 'Reduce slow @QuarkusTest usage with Mockito-first tests', and 'Convert repeated test methods to @ParameterizedTest', giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Has a clear Quarkus-specific niche and actively reduces conflict by redirecting generic Java work to 'For framework-agnostic Java use @131-java-testing-unit-testing', making wrong-skill triggering unlikely.	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/cursor-rules-java
Commit: 89b82c7

Reviewed: 2 days 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.