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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/421-frameworks-quarkus-testing-unit-tests/SKILL.md

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 a clear validated workflow and a single well-signaled reference file. Weaker on actionability and conciseness because the in-body guidance mostly restates the description and defers concrete test patterns to the reference.

Suggestions

Remove the 'When to use this skill' section or the 'What is covered' list, since both duplicate the frontmatter description; keep only what adds new guidance.

Add one small in-body example (e.g. a minimal @ExtendWith(MockitoExtension.class) test or an @InjectMock snippet) so the skill is actionable without opening the reference.

Make workflow step 3 ('Apply framework-aligned changes') concrete by naming the specific reference subsections to consult for each improvement type.

Dimension	Reasoning	Score
Conciseness	The body is reasonably lean and does not explain concepts Claude already knows, but the 'What is covered in this Skill?' and 'When to use this skill' sections largely restate the description, adding duplication rather than new value.	2 / 3
Actionability	Concrete build commands are present (./mvnw compile, mvn clean verify), but the actual testing patterns are deferred to the reference and the workflow steps themselves are abstract ('Implement or refactor configuration/code following the reference patterns').	2 / 3
Workflow Clarity	A clear 4-step sequence (read reference -> gather scope -> apply changes -> verify) with explicit validation checkpoints: compile before changes, stop immediately on compilation failure, and run clean verify after.	3 / 3
Progressive Disclosure	The body is an overview pointing to a single one-level-deep reference (references/421-frameworks-quarkus-testing-unit-tests.md, which exists), clearly signaled via both the workflow step and a Reference link, with content appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 strong, specific description with explicit trigger guidance and clear differentiation from the framework-agnostic sibling skill. The only issue is second-person voice ('Use when you need to write'), which triggers the specificity penalty.

Suggestions

Rephrase in third person to avoid the voice penalty, e.g. 'Use when writing fast unit tests for Quarkus applications...' or 'Triggers when adding or improving unit tests in a Quarkus project...'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (@ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock, @InjectSpy, REST Assured, @ParameterizedTest, QuarkusTestProfile, naming conventions), but the description uses second-person voice ('Use when you need to write'), which the guidelines penalize by reducing specificity by 1.	2 / 3
Completeness	Clearly answers both what (the enumerated testing techniques) and when (explicit 'Use when...' clause plus a 'This should trigger for requests such as' list).	3 / 3
Trigger Term Quality	Natural trigger phrases a user would say are present: 'Add or improve unit tests in a Quarkus project', 'Reduce slow @QuarkusTest usage with Mockito-first tests', 'Write fast pure unit tests for Quarkus services'.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to Quarkus unit testing and explicitly forks framework-agnostic Java to '@131-java-testing-unit-testing', making conflict with sibling skills unlikely.	3 / 3
	Total	11 / 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
Path: skills/421-frameworks-quarkus-testing-unit-tests/SKILL.md
Commit: fdaf68c

Reviewed: about 18 hours 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.