321 Frameworks Spring Boot Testing Unit Tests

Community

jabrena

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

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

Overview

Publisher	jabrena
Repository	`plinth`
Skill name	`321-frameworks-spring-boot-testing-unit-tests`
Stars	455
Forks	95
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jabrena on GitHub. Read the source before you install it.

Installation

Install the 321 Frameworks Spring Boot Testing Unit Tests AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jabrena/plinth/tree/main/skills/321-frameworks-spring-boot-testing-unit-tests
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jabrena/plinth/tree/main/skills/321-frameworks-spring-boot-testing-unit-tests

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jabrena/plinth.git /tmp/plinth
mkdir -p .claude/skills
cp -r /tmp/plinth/skills/321-frameworks-spring-boot-testing-unit-tests .claude/skills/321-frameworks-spring-boot-testing-unit-tests

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 321 Frameworks Spring Boot Testing Unit Tests in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 321 Frameworks Spring Boot Testing Unit Tests on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 321 Frameworks Spring Boot Testing Unit Tests is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/321-frameworks-spring-boot-testing-unit-tests.md33 KB

Frequently asked questions

What does the 321 Frameworks Spring Boot Testing Unit Tests AI skill do?

Why use 321 Frameworks Spring Boot Testing Unit Tests on TypingMind?

Because you install it once and use it with any model. 321 Frameworks Spring Boot Testing Unit Tests is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 321 Frameworks Spring Boot Testing Unit Tests in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jabrena/plinth/tree/main/skills/321-frameworks-spring-boot-testing-unit-tests. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 321 Frameworks Spring Boot Testing Unit Tests?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 321 Frameworks Spring Boot Testing Unit Tests?

As many as you like. As long as a model supports skills, you can use 321 Frameworks Spring Boot Testing Unit Tests with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 321 Frameworks Spring Boot Testing Unit Tests AI skill free?

Yes. It is published on GitHub by jabrena under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Graincrawl

openclaw

OrganizationPopular

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Spring Boot Unit Testing with Mockito

Constraints

When to use this skill

Workflow

Reference

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now