323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires .feature file in context. 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/323-frameworks-spring-boot-testing-acceptance-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, well-crafted skill description that clearly defines a narrow, specific use case with explicit trigger guidance. It names concrete technologies, actions, and prerequisites, making it easy for Claude to select this skill precisely when needed. The only minor note is the use of second-person 'you' in 'you need to', but since the rubric penalizes first/second person on specificity and the description is otherwise excellent, the impact is minimal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, using @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement acceptance tests from Gherkin feature files with specific technologies) and 'when' (opens with 'Use when you need to implement acceptance tests from a Gherkin .feature file'). Also specifies a prerequisite: 'Requires .feature file in context.' | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'Gherkin', '.feature file', 'acceptance tests', 'Spring Boot', 'TestRestTemplate', 'Testcontainers', 'WireMock', 'Kafka', '@acceptance'. These are all terms a Java developer would naturally mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Spring Boot acceptance tests from Gherkin feature files with a specific tech stack (Testcontainers, WireMock, TestRestTemplate). Very unlikely to conflict with other skills due to the precise combination of technologies and the @acceptance tag focus. | 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 has good structure and progressive disclosure, correctly pointing to a reference file for detailed content. However, it critically lacks any concrete code examples or executable guidance in the main body — it reads more like a table of contents than an actionable skill. The workflow has basic safety checks but misses the actual implementation steps.
Suggestions
Add at least one complete, executable code example showing a minimal acceptance test class with @SpringBootTest, TestRestTemplate, and a Testcontainer with @ServiceConnection — this is the core deliverable and should be visible without consulting the reference.
Include a concrete step-by-step workflow for implementing a test from a Gherkin scenario: (1) identify @acceptance scenario, (2) create test class with specific annotations, (3) map Given/When/Then to setup/call/assert, (4) run and validate.
Remove or condense the 'What is covered' bullet list — most items describe concepts Claude already knows (e.g., what TestRestTemplate does). Replace with a brief summary and let the code example demonstrate the patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat verbose and reads like a feature catalog rather than actionable instruction. Some items explain things Claude already knows (e.g., 'TestRestTemplate for REST API testing over the full servlet/filter stack'). The content could be tightened significantly. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic 'mvn compile', and no specific patterns showing how to structure a test class, configure Testcontainers, or set up WireMock stubs. The skill describes what to do but doesn't show how, deferring everything to the reference file. | 1 / 3 |
Workflow Clarity | The constraints section provides a basic sequence (compile → apply changes → verify) with a safety stop on compilation failure, which is good. However, the workflow lacks detail on the actual test implementation steps (parsing feature file → creating test class → configuring containers → writing assertions) and has no explicit feedback loop for test failures. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with a single, well-signaled reference to the detailed guide. The structure is clean with distinct sections (overview, constraints, when to use, reference) and the reference is one level deep. | 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
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.