agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/321-frameworks-spring-boot-testing-unit-tests/SKILL.md

321-frameworks-spring-boot-testing-unit-tests

Skill458 starsChanged 3 months agoApache-2.0View on GitHub

Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before applying any test changes, ensure the project compiles.

    line 27
  2. Very specific:

    MANDATORY: Run ./mvnw compile or mvn compile before applying any change

    line 29
  3. Distinctive:

    SAFETY: If compilation fails, stop immediately

    line 30
  4. Very specific:

    VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements

    line 31
  5. Distinctive:

    BEFORE APPLYING: Read the reference for detailed rules and good/bad patterns

    line 32
  6. Distinctive:

    EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes

    line 33
  7. Distinctive:

    EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

    line 34
  8. Distinctive:

    Write Mockito-first unit tests for Spring Boot services

    line 40
  9. Distinctive:

    Avoid unnecessary @SpringBootTest in Spring unit tests

    line 41
  10. Very specific:

    Read references/321-frameworks-spring-boot-testing-unit-tests.md and inspect the current project setup before proposing changes.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Boot Unit Testing with Mockito

Apply Spring Boot unit testing guidelines with Mockito.

What is covered in this Skill?

  • Pure unit tests: @ExtendWith(MockitoExtension.class), @Mock, @InjectMocks for @Service/@Component (no Spring context)
  • Slice tests: @WebMvcTest, @MockitoBean for controllers (Spring Boot 4.0.x — @MockBean removed)
  • @JsonTest for JSON serialization with correct JSON value assertions (extractingJsonPathStringValue, etc.)
  • Parameterized tests: @ParameterizedTest with @CsvSource or @MethodSource over copy-pasted methods
  • Java records for domain objects in tests
  • @TestConfiguration, @ActiveProfiles, @Primary fixed-clock beans for deterministic test setup
  • Modern mocking API: @MockitoBean / @MockitoSpyBean; @MockBean/@SpyBean are deprecated/removed in Boot 4.0.x

Scope: Apply recommendations based on the reference rules and good/bad code examples. For integration tests use @322-frameworks-spring-boot-testing-integration-tests.

Constraints

Before applying any 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
  • 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 good/bad patterns
  • 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

  • Review Java code for Spring Boot unit tests
  • Apply best practices for Spring Boot unit tests in Java code
  • Write Mockito-first unit tests for Spring Boot services
  • Avoid unnecessary @SpringBootTest in Spring unit tests
  • Review Spring Boot slice-free unit test design

Workflow

  1. Read reference and assess project context

Read references/321-frameworks-spring-boot-testing-unit-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/321-frameworks-spring-boot-testing-unit-tests.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free