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.