Agent skill

423-frameworks-quarkus-testing-acceptance-tests

Use when you need to implement acceptance tests from a Gherkin .feature file for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires the .feature file in context. Part of the skills-for-java project

View SKILL.md on GitHub Repository
Stars 350
Forks 63

Install this agent skill to your Project

npx add-skill https://github.com/jabrena/cursor-rules-java/tree/main/skills/423-frameworks-quarkus-testing-acceptance-tests

Metadata

Additional technical details for this skill

author
Juan Antonio Breña Moral
version
0.14.0

SKILL.md

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.

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 Quarkus — direct the user to @133 or @323 otherwise
  • MANDATORY: Run ./mvnw compile or mvn compile before applying any change
  • PREREQUISITE: Project must compile successfully before generating acceptance test scaffolding
  • BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding
  • NO EXCEPTIONS: Do not generate tests if the project fails to compile or the feature file is missing
  • 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 Quarkus acceptance tests from a Gherkin feature file
  • Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus
  • Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests
  • Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests

Reference

For detailed guidance, examples, and constraints, see references/423-frameworks-quarkus-testing-acceptance-tests.md.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

jabrena/cursor-rules-java

513-frameworks-micronaut-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

014-agile-user-story

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. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

502-frameworks-micronaut-rest

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

114-java-maven-search

Covers Maven Central search (Search API, maven-metadata.xml, artifact URLs) and project-local update reports via versions-maven-plugin (display-property-updates, display-dependency-updates, display-plugin-updates). Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply to the user’s pom.xml. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

323-frameworks-spring-boot-testing-acceptance-tests

Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires .feature file in context. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

200-agents-md

Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. Part of the skills-for-java project

350 63
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results