Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest; Write @MicronautTest integration tests with Testcontainers; Configure replacement beans for Mi
SkillScore77Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/20/2026
What it changes
Passed 12 of 16 test cases with the skill, and 8 of 16 without it.
Without skill50%
With skill77%
Checks it passed that the model alone missed
Recommends static container instances shared per test class
Recommends running `./mvnw clean verify` or `mvn clean verify`
Recommends suffixing integration test class names with `IT` or `AT`
and 3 more in the full report
6 fixed11 passed either way5 still failing0 broke
Pass-rate lift
+27 pp
Tokens
-11%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/20/2026v117 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
We finished configuring dynamic properties with TestPropertyProvider for our Redis integration tests in our Micronaut service. What exact Maven phase command must be executed to verify the build and run all integration tests completely?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends running `./mvnw clean verify` or `mvn clean verify`
Missed
Passed
case-05 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md56 lines2 files
Micronaut Integration Testing
Prove real wiring in Micronaut with containers and HTTP.
What is covered in this Skill?
Scope: contracts and boundaries, not duplicated unit-test logic
TestPropertyProvider + static @Container for JDBC/Kafka properties
HttpClient full-stack HTTP assertions
@MicronautTest(transactional = true) for rollback where supported
Shared containers per class; pinned image tags
Maven Surefire/Failsafe: *Test / *Tests vs *IT / *AT; explicit plugin includes and excludes
Scope: Apply recommendations based on the reference rules and good/bad code examples.
Constraints
Before applying any integration test changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification.
MANDATORY: Run ./mvnw compile or mvn compile before applying any change
PREREQUISITE: Project must compile successfully and pass basic validation checks before any test refactoring
CRITICAL SAFETY: If compilation fails, IMMEDIATELY STOP and DO NOT CONTINUE with any recommendations
BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding with integration test changes
NO EXCEPTIONS: Under no circumstances should testing recommendations be applied to a project that fails to compile
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed rules and examples
When to use this skill
Add Micronaut integration tests with Testcontainers
Wire dynamic datasource or broker URLs for @MicronautTest
Write @MicronautTest integration tests with Testcontainers
Configure replacement beans for Micronaut integration tests
Review Micronaut integration test lifecycle and resources
Workflow
Read reference and assess project context
Read references/522-frameworks-micronaut-testing-integration-tests.md and inspect the current project setup before proposing changes.
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design or review WireMock stubs (JSON mappings or Java DSL); Improve request matching, isolation, or reset strategy f