How do I install the 522 Frameworks Micronaut Testing Integration Tests skill?

Run npx skillmds add majiayu000/522-frameworks-micronaut-testing-integration-tests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 522 Frameworks Micronaut Testing Integration Tests safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 522 Frameworks Micronaut Testing Integration Tests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 522 Frameworks Micronaut Testing Integration Tests free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 522 Frameworks Micronaut Testing Integration Tests?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

522 Frameworks Micronaut Testing Integration Tests by majiayu000

Name: 522 Frameworks Micronaut Testing Integration Tests
Rating: 4.2 (5 reviews)
Author: majiayu000

522 Frameworks Micronaut Testing Integration Tests

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. Part of cursor-rules-java project

majiayu000 e62914f 2 files · 3.9 KB Updated Sep 9, 2026 567 repo stars

File contents

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

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.

Gather scope and decide target improvements

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

Apply framework-aligned changes

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

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/522-frameworks-micronaut-testing-integration-tests.md.

---name: 522-frameworks-micronaut-testing-integration-testsdescription: 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. Part of cursor-rules-java projectlicense: Apache-2.0---# 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 ## Workflow 1. **Read reference and assess project context** Read `references/522-frameworks-micronaut-testing-integration-tests.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor configuration/code following the reference patterns and project conventions. 4. **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/522-frameworks-micronaut-testing-integration-tests.md](references/522-frameworks-micronaut-testing-integration-tests.md).

Frequently asked questions