Micronaut acceptance tests from Gherkin

• 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

Constraints

• 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

Reference