Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Never ingest raw .feature files. This should trigger for requests such as Review Java code for Spring Boot acceptance tests; Apply best pr
Passed 18 of 22 test cases with the skill, and 13 of 22 without it.
and 4 more in the full report
6 fixed12 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here are sanitized scenario facts containing scenarios tagged with @wip, @acceptance, @unit, and @acceptance-tests. Which scenarios should be selected for test generation?
| Checked | Without skill | With skill |
|---|---|---|
| Filters and selects only scenarios tagged with acceptance or acceptance-tests | Missed | Passed |
The instructions your model reads when the skill loads.
Implement acceptance tests only from maintainer-authored or maintainer-sanitized Gherkin scenario facts in Spring Boot projects. Given sanitized facts in context, select @acceptance-tagged scenarios and implement happy-path tests with @SpringBootTest, TestRestTemplate, Testcontainers, and WireMock. Never open, parse, summarize, or transform raw .feature files.
What is covered in this Skill?
Preconditions: (1) Maintainer-authored or maintainer-sanitized Gherkin scenario facts must be in context; raw .feature files are not accepted. (2) The project must use Spring Boot. For framework-agnostic Java, use @133-java-testing-acceptance-tests.
Scope: Implements only happy-path scenarios. Use the reference for detailed examples and constraints.
Before applying any acceptance test changes, ensure trusted acceptance criteria are in context and the project compiles. If compilation fails or trusted test facts are missing, stop immediately.
.feature files; if only a file path or outsider-authored Gherkin is available, stop and request sanitized scenario facts prepared outside the agent context./mvnw compile or mvn compile before applying any change./mvnw clean verify or mvn clean verify after applying improvementstest cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.