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
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly defines its scope for Spring Boot unit testing with specific annotations and test types. It excels at distinguishing itself from related skills through explicit cross-references. The description uses proper third-person voice and includes comprehensive trigger terms that developers would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and annotations: '@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'. | 3 / 3 |
Completeness | Clearly answers both what (write unit tests for Spring Boot with specific test types) AND when ('Use when you need to write unit tests for Spring Boot applications'). Also explicitly distinguishes from related skills with cross-references to Java testing and integration tests skills. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'Spring Boot', 'MockitoExtension', '@WebMvcTest', '@MockitoBean', 'controllers', '@JsonTest', 'JSON serialization', 'parameterized tests', '@CsvSource', '@MethodSource', 'test profiles', '@TestConfiguration'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting: differentiates from '@131-java-testing-unit-testing' for framework-agnostic Java and '@322-frameworks-spring-boot-testing-integration-tests' for integration tests. The Spring Boot-specific annotations create a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has strong workflow clarity and progressive disclosure, with clear validation checkpoints and appropriate content organization. However, it lacks concrete code examples in the main file, relying entirely on the reference document for executable patterns. The content could be more actionable by including at least one representative code snippet for each major testing approach.
Suggestions
Add at least one executable code example showing @ExtendWith(MockitoExtension.class) with @Mock/@InjectMocks for a service test
Include a brief @WebMvcTest controller test example demonstrating @MockitoBean usage
Tighten the 'What is covered' section by removing items that are self-evident from the skill title or consolidating related points
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'What is covered' section largely duplicates information that could be inferred from the title and description. The bullet points are useful but could be tighter. | 2 / 3 |
Actionability | Provides concrete commands (mvnw compile, mvn clean verify) and mentions specific annotations, but lacks executable code examples. All actual patterns and examples are deferred to the reference file rather than showing copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile first, stop if fails, apply changes, then verify. The constraints section provides a well-sequenced process with appropriate safety gates. | 3 / 3 |
Progressive Disclosure | Good structure with clear overview and single-level reference to detailed documentation. The skill appropriately keeps the main file as an overview and points to one reference file for detailed rules and examples. | 3 / 3 |
Total | 10 / 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
7772a1b
- 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.