How do I install the 521 Frameworks Micronaut Testing Unit Tests skill?

Run npx skillmds add majiayu000/521-frameworks-micronaut-testing-unit-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 521 Frameworks Micronaut Testing Unit 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 521 Frameworks Micronaut Testing Unit 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 521 Frameworks Micronaut Testing Unit Tests free to use?

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

Who published 521 Frameworks Micronaut Testing Unit Tests?

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

521 Frameworks Micronaut Testing Unit Tests by majiayu000

Name: 521 Frameworks Micronaut Testing Unit Tests
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

521 Frameworks Micronaut Testing Unit Tests

Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests. Part of cursor-rules-java project

majiayu000 c7261f0 2 files · 3.7 KB Updated Sep 9, 2026 567 repo stars

File contents

Micronaut Unit Testing

Apply fast testing strategies for Micronaut: Mockito-first, narrow @MicronautTest when HTTP or DI replacement is required.

What is covered in this Skill?

Pure JUnit 5 + Mockito without container boot
@MicronautTest with @MockBean factory methods for collaborators
HttpClient blocking exchanges against the embedded server
@Property for deterministic configuration in tests
@ParameterizedTest with @CsvSource / @MethodSource
Naming: *Test → Surefire; *IT → Failsafe when configured
When to escalate to @522

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

Constraints

Compile before test refactors; verify the full suite after.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed rules and examples
EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

When to use this skill

Add or improve unit tests in a Micronaut project
Reduce unnecessary @MicronautTest usage with Mockito-first tests

Workflow

Read reference and assess project context

Read references/521-frameworks-micronaut-testing-unit-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/521-frameworks-micronaut-testing-unit-tests.md.

---name: 521-frameworks-micronaut-testing-unit-testsdescription: Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests. Part of cursor-rules-java projectlicense: Apache-2.0---# Micronaut Unit Testing Apply fast testing strategies for Micronaut: Mockito-first, narrow @MicronautTest when HTTP or DI replacement is required. **What is covered in this Skill?** - Pure JUnit 5 + Mockito without container boot - @MicronautTest with @MockBean factory methods for collaborators - HttpClient blocking exchanges against the embedded server - @Property for deterministic configuration in tests - @ParameterizedTest with @CsvSource / @MethodSource - Naming: *Test → Surefire; *IT → Failsafe when configured - When to escalate to `@522` **Scope:** Apply recommendations based on the reference rules and good/bad code examples. ## Constraints Compile before test refactors; verify the full suite after. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and examples - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Add or improve unit tests in a Micronaut project - Reduce unnecessary @MicronautTest usage with Mockito-first tests ## Workflow 1. **Read reference and assess project context** Read `references/521-frameworks-micronaut-testing-unit-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/521-frameworks-micronaut-testing-unit-tests.md](references/521-frameworks-micronaut-testing-unit-tests.md).

Frequently asked questions