323-frameworks-spring-boot-testing-acceptance-tests
This Claude Code skill implements acceptance tests from Gherkin feature files in Spring Boot applications. Use it when you need to create happy-path acceptance tests that parse @acceptance-tagged scenarios and set up test infrastructure including @SpringBootTest with TestRestTemplate, Testcontainers with @ServiceConnection for databases and message brokers, and WireMock stubs for external REST APIs. Requires a .feature file in the project context and Spring Boot as the framework.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/323-frameworks-spring-boot-testing-acceptance-tests && cp -r /tmp/323-frameworks-spring-boot-testing-acceptance-tests/skills/323-frameworks-spring-boot-testing-acceptance-tests ~/.claude/skills/323-frameworks-spring-boot-testing-acceptance-testsSKILL.md
# Spring Boot acceptance tests from Gherkin Implement acceptance tests from Gherkin feature files in Spring Boot projects. Given a .feature file in context, find @acceptance-tagged scenarios and implement happy-path tests with @SpringBootTest, TestRestTemplate, Testcontainers, and WireMock. **What is covered in this Skill?** - Parse Gherkin .feature files to find scenarios tagged @acceptance or @acceptance-tests - Implement happy-path acceptance tests (one test per scenario) - @SpringBootTest(webEnvironment = RANDOM_PORT), @Autowired TestRestTemplate (auto-configured, no extra dependency) - @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) The Gherkin .feature file must be in context. (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 the Gherkin .feature file is in context and the project compiles. If compilation fails or the feature file is missing, stop immediately. - **PRECONDITION**: The Gherkin .feature file MUST be in context; the project MUST use Spring Boot - **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 ## 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](references/323-frameworks-spring-boot-testing-acceptance-tests.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project