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. Part of the skills-for-java project
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that excels at specificity and completeness, with explicit 'Use when' guidance and helpful cross-referencing to related skills. The main weakness is that trigger terms lean heavily on technical jargon that developers familiar with Quarkus would use, but may miss more casual phrasings. The description effectively carves out a distinct niche within Java testing skills.
Suggestions
Add more natural user phrases alongside technical terms, such as 'test my Quarkus app', 'mock CDI beans', or 'test REST endpoints in Quarkus'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and techniques: '@ExtendWith(MockitoExtension.class)', '@QuarkusTest with @InjectMock', '@InjectSpy', 'REST Assured', '@ParameterizedTest with @CsvSource / @MethodSource', 'QuarkusTestProfile', and naming conventions for Surefire/Failsafe. | 3 / 3 |
Completeness | Clearly answers both what (write fast unit tests with specific Quarkus testing patterns) and when ('Use when you need to write fast unit tests for Quarkus applications'). Also provides helpful disambiguation pointing to another skill for framework-agnostic Java. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Quarkus', 'unit tests', 'CDI', 'REST Assured', but these are framework-specific jargon. Missing more natural user phrases like 'test my Quarkus app', 'mock beans', or 'testing endpoints'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear Quarkus-specific focus and explicit disambiguation from generic Java testing skill (@131-java-testing-unit-testing). The Quarkus-specific annotations and patterns create a clear niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates excellent organization, conciseness, and workflow clarity with proper validation checkpoints. The main weakness is the lack of inline executable code examples - all concrete guidance is deferred to the reference file, which reduces immediate actionability for common use cases.
Suggestions
Add 1-2 minimal executable code examples inline (e.g., a pure Mockito test and a @QuarkusTest with @InjectMock) to make the skill immediately actionable without requiring reference file lookup
Include a brief code snippet showing the @ParameterizedTest with @CsvSource pattern since it's explicitly listed as a covered topic
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to list capabilities without explaining what Mockito or JUnit are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides clear guidance on when to use different testing approaches and naming conventions, but lacks executable code examples. All concrete examples are deferred to the reference file rather than providing copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile before changes, stop if compilation fails, verify after improvements. The MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION structure makes the sequence unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear 'What is covered' section, explicit constraints, usage triggers, and a single well-signaled reference link for detailed rules and examples. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
b36efb2
- Reviewed
Table of Contents
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.