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
77
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/521-frameworks-micronaut-testing-unit-tests/SKILL.mdApply fast testing strategies for Micronaut: Mockito-first, narrow @MicronautTest when HTTP or DI replacement is required.
What is covered in this Skill?
@522Scope: Apply recommendations based on the reference rules and good/bad code examples.
Compile before test refactors; verify the full suite after.
./mvnw compile or mvn compile before applying any change./mvnw clean verify or mvn clean verify after applying improvementsRead references/521-frameworks-micronaut-testing-unit-tests.md and inspect the current project setup before proposing changes.
Identify requested outcomes, constraints, and the minimum safe set of changes to apply.
Implement or refactor configuration/code following the reference patterns and project conventions.
Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.
For detailed guidance, examples, and constraints, see references/521-frameworks-micronaut-testing-unit-tests.md.
899d988
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.