Quarkus acceptance tests from Gherkin

Implement happy-path acceptance tests from Gherkin for Quarkus using real HTTP and infrastructure.

What is covered in this Skill?

• Preconditions: .feature file in context; Quarkus project confirmed
• Parsing and filtering scenarios tagged @acceptance / @acceptance-tests
• BaseAcceptanceTest with @QuarkusTest, @QuarkusTestResource, and QuarkusTestResourceLifecycleManager for:
  • Testcontainers (PostgreSQL, Kafka) with dynamic config injection on startup
  • WireMock with wireMockServer.resetAll() in @BeforeEach to isolate stubs
• Concrete acceptance test class extending BaseAcceptanceTest:
  • @DisplayName mirroring the Gherkin scenario title
  • Given (stubs + fixtures) / When (REST Assured HTTP call) / Then (response assertions + wireMock.verify)
• WireMock JSON mapping files under classpath:wiremock/mappings/ with body files under __files/
• Naming convention: *AT suffix for Failsafe; never *Test (Surefire) or *AcceptanceTest
• Maven three-tier split: *Test → Surefire, *IT + *AT → Failsafe
• Happy-path scope by default; escalate to negatives only when explicitly requested

Scope: Apply recommendations based on the reference rules and step workflow.