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
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/421-frameworks-quarkus-testing-unit-tests/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that is highly specific, includes rich trigger terms natural to Quarkus developers, clearly states both what it does and when to use it, and explicitly disambiguates from a related skill. The only minor note is that it's quite dense, but the information density serves the purpose of skill selection well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: @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 for Quarkus applications with specific testing patterns) and 'when' (opens with 'Use when you need to write fast unit tests for Quarkus applications'). Also includes a disambiguation clause pointing to a different skill for framework-agnostic Java testing. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a Quarkus developer would use: 'unit tests', 'Quarkus', '@QuarkusTest', '@InjectMock', '@InjectSpy', 'REST Assured', '@ParameterizedTest', 'QuarkusTestProfile', 'Surefire', 'Failsafe', 'CDI mock'. These are highly specific and natural keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Quarkus-specific triggers (@QuarkusTest, @InjectMock, @InjectSpy, QuarkusTestProfile) and explicitly disambiguates from the generic Java testing skill (@131-java-testing-unit-testing), making conflicts very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a table of contents pointing to a reference file, with almost no actionable content in the body itself. While the progressive disclosure and basic workflow structure are reasonable, the complete absence of concrete code examples or executable guidance severely limits its usefulness. The 'What is covered' section is verbose relative to the value it provides, essentially duplicating the skill description.
Suggestions
Add at least 2-3 minimal, executable code examples for the most common patterns (e.g., a pure Mockito test, a @QuarkusTest with @InjectMock, and a REST Assured test) so Claude has actionable guidance without needing to read the reference file.
Remove or significantly condense the 'What is covered' bullet list — it restates the description without adding actionable value. Replace it with a quick-start example.
Add a validation/feedback loop step for when tests fail after refactoring (e.g., 'If tests fail: review failures, fix, re-run ./mvnw test before proceeding to next refactor').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes a verbose 'What is covered' bullet list that largely restates the description and frontmatter. The table-of-contents style listing doesn't add actionable value beyond what the section headers or reference file would provide. | 2 / 3 |
Actionability | There are no concrete code examples, executable commands (beyond generic mvnw compile), or copy-paste ready snippets. The skill describes what topics exist but delegates all actual guidance to the reference file, leaving Claude with no actionable content in the skill itself. | 1 / 3 |
Workflow Clarity | The Constraints section provides a reasonable sequence (compile → apply changes → verify) with a stop condition on compilation failure, but lacks explicit validation checkpoints between test refactoring steps and no feedback loop for test failures after changes. | 2 / 3 |
Progressive Disclosure | The skill is structured as a clear overview with a single, well-signaled reference link to the detailed guidance file. Navigation is one level deep and clearly indicated. | 3 / 3 |
Total | 8 / 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
1847adc
- 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.