v0.15.0-SNAPSHOT to v0.15.0

1 added, 1 removed. Audit A to A.

---
name: 523-frameworks-micronaut-testing-acceptance-tests
description: Use when you need to implement acceptance tests from a Gherkin .feature file for Micronaut applications — @acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider for Testcontainers and WireMock, *AT suffix, Failsafe. Requires the .feature file in context. This should trigger for requests such as Implement Micronaut acceptance tests from a Gherkin feature file; Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut. Part of cursor-rules-java project
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
- version: 0.15.0-SNAPSHOT
+ version: 0.15.0
---
# Micronaut acceptance tests from Gherkin
Implement happy-path acceptance tests from Gherkin for Micronaut using real HTTP and infrastructure.
**What is covered in this Skill?**
- Preconditions: .feature file in context; Micronaut project confirmed
- Parsing scenarios tagged @acceptance / @acceptance-tests
- BaseAcceptanceTest: @MicronautTest, random port, @Client(/) HttpClient, TestPropertyProvider merging DB + WireMock URLs
- wireMock.resetAll() in @BeforeEach when sharing context
- Concrete *AT classes: Given/When/Then → setup, HttpClient exchange, AssertJ assertions
- Maven three-tier split: *Test → Surefire, *IT + *AT → Failsafe
- Happy-path scope by default
**Scope:** Apply recommendations based on the reference rules and step workflow.
## Constraints
Do not generate without a .feature file; compile before and verify after.
- **PRECONDITION**: Gherkin `.feature` file must be in context — stop and ask if not provided
- **PRECONDITION**: The project must use Micronaut — direct the user to @133, @323, or @423 otherwise
- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed steps and safeguards
## When to use this skill
- Implement Micronaut acceptance tests from a Gherkin feature file
- Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut
## Workflow
1. **Read reference and assess project context**
Read `references/523-frameworks-micronaut-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/523-frameworks-micronaut-testing-acceptance-tests.md](references/523-frameworks-micronaut-testing-acceptance-tests.md).