422 Frameworks Quarkus Testing Integration Tests logo

422 Frameworks Quarkus Testing Integration Tests

Community
jabrena
422-frameworks-quarkus-testing-integration-tests

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of Plinth Toolkit

Overview

Publisherjabrena
Repositoryplinth
Skill name422-frameworks-quarkus-testing-integration-tests
Stars
455
Forks
95
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jabrena on GitHub. Read the source before you install it.

Installation

Install the 422 Frameworks Quarkus Testing Integration Tests AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jabrena/plinth/tree/main/skills/422-frameworks-quarkus-testing-integration-tests
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jabrena/plinth.git /tmp/plinth
mkdir -p .claude/skills
cp -r /tmp/plinth/skills/422-frameworks-quarkus-testing-integration-tests .claude/skills/422-frameworks-quarkus-testing-integration-tests
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 422 Frameworks Quarkus Testing Integration Tests in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 422 Frameworks Quarkus Testing Integration Tests on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 422 Frameworks Quarkus Testing Integration Tests is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Quarkus Integration Testing

Apply integration testing patterns for Quarkus with real wiring and reproducible infrastructure.

What is covered in this Skill?

  • @QuarkusTest for in-JVM integration with real CDI wiring
  • Dev Services for automatic container provisioning (%test.quarkus.datasource.devservices)
  • Testcontainers via QuarkusTestResourceLifecycleManager (start/stop lifecycle, dynamic config injection)
  • WireMock for stubbing external HTTP services via QuarkusTestResourceLifecycleManager
  • @QuarkusIntegrationTest for black-box testing against the packaged JAR or native binary
  • HTTP testing with REST Assured against the Quarkus test port
  • Data isolation: @TestTransaction for automatic rollback; @BeforeEach cleanup for HTTP tests
  • Maven three-tier split: *Test → Surefire (fast), *IT + *AT → Failsafe (verify)
  • Native-image test considerations with @DisabledOnNativeImage

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Compile before changes; verify after; Docker may be required for containers.

  • MANDATORY: Run ./mvnw compile or mvn compile before applying any change
  • PREREQUISITE: Project must compile before applying integration test improvements
  • SAFETY: If compilation fails, stop immediately
  • BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding
  • VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements; Docker is required for Testcontainers and Dev Services
  • BEFORE APPLYING: Read the reference for detailed rules and examples

When to use this skill

  • Add or improve integration tests in a Quarkus project
  • Configure Testcontainers or Dev Services for Quarkus tests
  • Add WireMock stubs for external HTTP dependencies in Quarkus integration tests
  • Set up @QuarkusIntegrationTest for packaged artifact or native binary testing
  • Fix test data isolation or configure Maven Surefire/Failsafe split

Workflow

  1. Read reference and assess project context

Read references/422-frameworks-quarkus-testing-integration-tests.md and inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

  1. 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/422-frameworks-quarkus-testing-integration-tests.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the 422 Frameworks Quarkus Testing Integration Tests AI skill do?

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for...

Why use 422 Frameworks Quarkus Testing Integration Tests on TypingMind?

Because you install it once and use it with any model. 422 Frameworks Quarkus Testing Integration Tests is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 422 Frameworks Quarkus Testing Integration Tests in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jabrena/plinth/tree/main/skills/422-frameworks-quarkus-testing-integration-tests. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 422 Frameworks Quarkus Testing Integration Tests?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 422 Frameworks Quarkus Testing Integration Tests?

As many as you like. As long as a model supports skills, you can use 422 Frameworks Quarkus Testing Integration Tests with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 422 Frameworks Quarkus Testing Integration Tests AI skill free?

Yes. It is published on GitHub by jabrena under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇