423-frameworks-quarkus-testing-acceptance-tests

Generate Quarkus acceptance tests from Gherkin scenarios with Testcontainers and WireMock.

423|90|Updated Feb 8, 2025
One-click install
npx skills add https://github.com/jabrena/plinth --skill 423-frameworks-quarkus-testing-acceptance-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 423-frameworks-quarkus-testing-acceptance-tests
Source: https://github.com/jabrena/plinth/tree/main/skills/423-frameworks-quarkus-testing-acceptance-tests
Command: npx skills add https://github.com/jabrena/plinth --skill 423-frameworks-quarkus-testing-acceptance-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires testcontainers, wiremock, maven-failsafe-plugin, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup and generation of acceptance tests for Quarkus applications, including configuring Testcontainers and WireMock, creating JSON mapping files, and applying Maven Surefire/Failsafe conventions, reducing the time and effort needed to write and maintain acceptance tests.

Core Features & Use Cases

  • Automated Test Generation: Based on sanitized Gherkin scenario facts, automatically generates Quarkus acceptance tests.
  • Configuration Management: Manages Testcontainers, WireMock, and Maven configurations for consistent testing environments.
  • Use Case: When developing Quarkus applications, use this Skill to generate acceptance tests that ensure the application meets specified requirements.

Quick Start

Run the generate-acceptance-tests command in the Quarkus project directory to start the test generation process.

Frequently Asked Questions about 423-frameworks-quarkus-testing-acceptance-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Quarkus acceptance test generation from Gherkin scenarios?

You can automate Quarkus acceptance test generation by feeding sanitized Gherkin scenario facts into this Skill. It automatically configures Testcontainers and WireMock, generates JSON mapping files, and applies Maven Surefire/Failsafe conventions to streamline the entire test setup process.

What is the best way to configure Testcontainers and WireMock for Quarkus acceptance tests?

The best way to configure Testcontainers and WireMock for Quarkus acceptance tests is using an automated generation tool. This Skill manages the configurations, creates necessary WireMock JSON mapping files, and ensures consistent testing environments across your Quarkus application.

How do I run generated acceptance tests in a Quarkus project using Maven?

To run generated acceptance tests in a Quarkus project, run the `generate-acceptance-tests` command in your project directory. The Skill applies Maven Failsafe plugin conventions to execute the tests, ensuring the application meets the specified requirements defined in your Gherkin scenarios.

Do I need sanitized Gherkin scenarios to generate Quarkus acceptance tests?

Yes, sanitized Gherkin scenario facts are required as input to generate Quarkus acceptance tests. The Skill uses these Gherkin facts as the foundation to automatically generate test code and configure Testcontainers, WireMock, and Maven for your Quarkus application.

Can I use WireMock and Testcontainers together for Quarkus application testing?

Yes, you can use WireMock and Testcontainers together for Quarkus application testing. This Skill configures both dependencies simultaneously, creating JSON mapping files for WireMock and managing Testcontainers configurations to provide isolated, consistent acceptance testing environments.

Why are Maven Surefire and Failsafe conventions needed for Quarkus acceptance tests?

Maven Surefire and Failsafe conventions are needed for Quarkus acceptance tests to separate unit tests from integration tests properly. This Skill applies these Maven conventions during test generation, ensuring your acceptance tests are executed in the correct phase of the build lifecycle.