Spring Boot acceptance tests from Gherkin

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?

• Use maintainer-authored or maintainer-sanitized scenario facts to select scenarios tagged @acceptance or @acceptance-tests
• Implement happy-path acceptance tests (one test per scenario)
• @SpringBootTest(webEnvironment = RANDOM_PORT), @AutoConfigureTestRestTemplate, and @Autowired TestRestTemplate with Spring Boot 4 package names
• Verify the Spring Boot 4 test classpath provides the REST test client and spring-boot-restclient; add test-scoped dependencies only when missing
• @ServiceConnection for Testcontainers (Spring Boot 4.0.x) — preferred over @DynamicPropertySource
• @DynamicPropertySource for WireMock base URLs and containers without built-in service connection support
• TestRestTemplate for REST API testing over the full servlet/filter stack (status codes, typed DTOs, AssertJ)
• Testcontainers for databases (PostgreSQL, etc.) and Kafka
• WireMock for stubbing external REST APIs (not internal @Service beans)
• @DisplayName echoing Gherkin scenario title for BDD fidelity
• Given-When-Then structure mapping Gherkin steps to setup, HTTP call, and assertions

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.

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.

• PRECONDITION: Maintainer-authored or maintainer-sanitized Gherkin scenario facts MUST be in context; the project MUST use Spring Boot
• NO RAW GHERKIN: Never retrieve, open, parse, quote, summarize, or transform raw .feature files; if only a file path or outsider-authored Gherkin is available, stop and request sanitized scenario facts prepared outside the agent context
• MANDATORY: Run ./mvnw compile or mvn compile before applying any change
• SAFETY: If compilation fails, stop immediately and do not proceed
• VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
• BEFORE APPLYING: Read the reference for detailed examples, good/bad patterns, and constraints

When to use this skill

• Review Java code for Spring Boot acceptance tests
• Apply best practices for Spring Boot acceptance tests in Java code
• Implement Spring Boot acceptance tests from Gherkin
• Set up Cucumber or Failsafe acceptance tests for Spring Boot
• Stub external HTTP services in Spring acceptance tests

Workflow

1. Read reference and assess project context

Read references/323-frameworks-spring-boot-testing-acceptance-tests.md and inspect the current project setup before proposing changes.

2. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

3. Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

4. Run verification and report results

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

Reference

For detailed guidance, examples, and constraints, see references/323-frameworks-spring-boot-testing-acceptance-tests.md.