133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — finding @acceptance scenarios, happy path with RestAssured, Testcontainers for DB/Kafka, WireMock for external REST. 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/133-java-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 an excellent skill description that clearly defines its scope, tools, and trigger conditions. It uses third person voice appropriately, provides specific technical details without being overly verbose, and explicitly states when to use it. The explicit exclusion of frameworks and requirement for .feature file context further sharpens its distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'implement acceptance tests', 'finding @acceptance scenarios', 'happy path with RestAssured', 'Testcontainers for DB/Kafka', 'WireMock for external REST'. Very detailed about the technical stack and approach. | 3 / 3 |
Completeness | Clearly answers both what (implement acceptance tests with specific tools) and when ('Use when you need to implement acceptance tests from a Gherkin .feature file'). Includes explicit trigger guidance and prerequisites ('Requires .feature file in context'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'acceptance tests', 'Gherkin', '.feature file', 'Java', 'RestAssured', 'Testcontainers', 'WireMock', 'DB/Kafka'. Users working in this domain would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: framework-agnostic Java (explicitly excludes Spring Boot, Quarkus, Micronaut), specific to Gherkin acceptance tests, and names exact tools. Very unlikely to conflict with other testing or Java skills. | 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 provides a reasonable overview and good progressive disclosure to a reference file, but critically lacks actionable content. The main body describes what acceptance tests should cover without providing any executable code examples or concrete implementation guidance. The skill essentially serves as a pointer to the reference file rather than a standalone resource.
Suggestions
Add at least one complete, executable code example showing a basic acceptance test implementation with RestAssured and Testcontainers
Include a concrete example of mapping a Gherkin scenario to test code (show a sample Given-When-Then scenario and its corresponding Java test method)
Remove explanatory content Claude already knows (e.g., what RestAssured does) and replace with specific patterns or gotchas unique to this project's approach
Add a numbered workflow for implementing a test from a Gherkin scenario: 1. Parse scenario, 2. Create test class extending BaseAcceptanceTest, 3. Implement setup, 4. Implement assertions, 5. Validate
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy - the 'What is covered' section largely repeats information that could be inferred from the title and description. The bullet list format is efficient, but some items explain concepts Claude already knows (e.g., 'RestAssured for REST API testing (given/when/then, status codes, JSON body assertions)'). | 2 / 3 |
Actionability | The skill lacks any concrete code examples, executable commands beyond basic Maven invocations, or copy-paste ready snippets. It describes what to do ('Implement happy-path acceptance tests') but doesn't show how with actual code. All detailed guidance is deferred to a reference file. | 1 / 3 |
Workflow Clarity | There's a basic workflow implied (compile -> apply changes -> verify), but the actual test implementation workflow is missing. The constraints section mentions validation steps (compile before, verify after), but there's no clear sequence for the core task of implementing tests from Gherkin scenarios. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content with a clear overview and a single, well-signaled reference to detailed documentation. The reference link is one level deep and clearly indicated for 'detailed examples, good/bad patterns, and constraints'. | 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
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.