321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. Part of the skills-for-java project
74
67%
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/321-frameworks-spring-boot-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 matching developer vocabulary, clearly states both what it does and when to use it, and explicitly delineates its boundaries relative to adjacent skills. The only minor note is the use of second person 'you need to' in the opening, but the rest of the description uses appropriate impersonal/third-person framing. Overall, this is a strong, well-crafted description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and annotations: pure unit tests with @ExtendWith(MockitoExtension.class), slice tests with @WebMvcTest and @MockitoBean, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. | 3 / 3 |
Completeness | Clearly answers both 'what' (write unit tests for Spring Boot applications with specific test types) and 'when' (opens with 'Use when you need to write unit tests for Spring Boot applications'). Also explicitly distinguishes when NOT to use it by pointing to related skills for framework-agnostic Java testing and integration tests. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'unit tests', 'Spring Boot', '@WebMvcTest', '@MockitoBean', 'controllers', '@Service/@Component', 'JSON serialization', 'parameterized tests', '@CsvSource', '@MethodSource', '@TestConfiguration'. These are exactly the terms a Java developer would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — explicitly scoped to Spring Boot unit/slice tests and clearly differentiates itself from framework-agnostic Java testing (@131) and Spring Boot integration tests (@322), minimizing overlap and conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill body is essentially a table of contents and a pointer to a reference file, with almost no actionable content of its own. While the compilation/verification constraints provide a useful safety workflow, the complete absence of code examples, concrete patterns, or inline guidance means Claude would need to read the reference file before being able to do anything. The skill would benefit significantly from at least one or two inline code examples showing the key patterns (e.g., a pure unit test with @ExtendWith, a slice test with @WebMvcTest).
Suggestions
Add at least 2-3 concrete, executable code examples inline — e.g., a minimal @ExtendWith(MockitoExtension.class) service test and a @WebMvcTest controller test — so the skill is actionable without requiring the reference file.
Replace the 'What is covered' bullet list with a brief quick-start section showing the most common pattern, then link to the reference for advanced topics.
Include a specific example of the @MockitoBean vs deprecated @MockBean migration pattern, since this is a key differentiator mentioned in the skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' section is essentially a bullet-point table of contents that restates what the skill does without providing actionable content. The scope note and some framing text are mildly redundant, but overall it's not excessively verbose. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns shown. All actual guidance is deferred to the reference file, leaving the skill body as a description rather than an instruction set. | 1 / 3 |
Workflow Clarity | The Constraints section provides a clear compile-first → apply → verify sequence with a stop-on-failure checkpoint, which is good. However, the actual testing workflow (how to write/structure tests) has no steps at all — it's entirely deferred to the reference file. | 2 / 3 |
Progressive Disclosure | There is a clear reference link to a detailed file, which is good one-level-deep disclosure. However, the skill body itself contains almost no substantive quick-start content — it's nearly all summary/TOC with everything deferred, making the overview too thin to be useful on its own. | 2 / 3 |
Total | 7 / 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
9ec21dd
- 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.