322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. 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/322-frameworks-spring-boot-testing-integration-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 a strong skill description that clearly identifies both when to use it and what it covers, with highly specific Spring Boot 4.0.x integration testing technologies and patterns. The trigger terms are natural and comprehensive for the target audience of Java/Spring developers. Minor note: it uses second person ('you need to') rather than third person voice, but the overall quality is excellent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management. These are highly specific capabilities. | 3 / 3 |
Completeness | Explicitly starts with 'Use when you need to write or improve integration tests' which clearly answers the 'when' question, and the rest of the description details the 'what' with specific technologies and patterns. Both dimensions are well covered. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords a developer would use: 'integration tests', 'Testcontainers', '@ServiceConnection', '@DataJdbcTest', 'TestRestTemplate', 'MockMvcTester', 'Spring Boot 4.0.x', 'data isolation', 'container lifecycle'. These are terms developers naturally mention when seeking help with Spring Boot testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Spring Boot 4.0.x, Testcontainers, @ServiceConnection, @DataJdbcTest, and other Spring-specific testing annotations. This is unlikely to conflict with general testing skills or other framework-specific skills. | 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.
This skill functions primarily as a table of contents pointing to a reference file, rather than providing actionable guidance in its own right. The constraints section adds some workflow value with compile/verify steps, but the complete absence of code examples or concrete patterns means Claude would need to read the reference file before being able to do anything useful. The skill would benefit significantly from including at least one or two concrete, executable examples inline.
Suggestions
Add at least 2-3 concrete, executable code examples inline — e.g., a Testcontainers + @ServiceConnection setup, a MockMvcTester assertion, and a @DataJdbcTest slice — so the skill body is actionable without requiring the reference file.
Include a brief workflow for writing a new integration test (e.g., 1. Choose slice annotation or @SpringBootTest, 2. Add container with @ServiceConnection, 3. Write test method, 4. Run verify) with explicit validation at each step.
Trim the 'What is covered' bullet list — it largely duplicates the reference file's purpose. Replace it with a quick-start example that demonstrates the most common pattern.
Add a concrete example of the @MockitoBean usage since it replaces the removed @MockBean, as this is a Spring Boot 4.0.x-specific change that Claude may not know about.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet-point list of 'What is covered' is somewhat verbose and reads more like a table of contents than actionable content. The parenthetical explanations (e.g., 'verify wiring and contracts, not unit-test duplication') add some value but the overall structure could be tighter. It doesn't over-explain concepts Claude knows, but the coverage list is largely a restatement of the description. | 2 / 3 |
Actionability | The skill contains no executable code examples, no concrete commands beyond generic mvnw invocations, and no specific patterns showing how to write integration tests. It describes what topics are covered but delegates all actual guidance to a reference file, leaving the skill body itself as vague direction rather than concrete instruction. | 1 / 3 |
Workflow Clarity | The Constraints section provides a clear sequence (compile → apply → verify) with a stop condition on failure, which is good. However, there are no validation checkpoints within the actual test-writing workflow itself, and the feedback loop for fixing issues is not explicit — it just says 'stop immediately' without recovery guidance. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a detailed file, which is good progressive disclosure. However, the skill body itself contains almost no substantive quick-start content — it's essentially just a topic list plus a pointer to the reference. A good progressive disclosure pattern would include at least a minimal executable example in the overview before pointing to the reference. | 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.