Agent skill

321 Frameworks Spring Boot Testing Unit Tests

by jabrena in jabrena/plinth

A skill your agent uses 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…

Apache-2.0Auto-check passedTesting & QA

Install 321 Frameworks Spring Boot Testing Unit Tests

skills CLI
$ npx skills add jabrena/plinth --skill 321-frameworks-spring-boot-testing-unit-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 321-frameworks-spring-boot-testing-unit-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/321-frameworks-spring-boot-testing-unit-tests .claude/skills/321-frameworks-spring-boot-testing-unit-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
321-frameworks-spring-boot-testing-unit-tests
GitHub stars
446
Token cost
~952 tokens
SKILL.md length
335 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • Slice tests with @WebMvcTest and @MockitoBean for controllers
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Calls mvn
  • @JsonTest for JSON serialization

What it does

321 Frameworks Spring Boot Testing Unit Tests is an agent skill from jabrena/plinth. 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…

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/321-frameworks-spring-boot-testing-unit-tests.md`).

It sits in Testing & QA, covering Unit testing and Backend development. It works with Spring Boot and Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • Slice tests with @WebMvcTest and @MockitoBean for controllers
  • @JsonTest for JSON serialization
  • Parameterized tests with @CsvSource/@MethodSource
  • @TestConfiguration

Example prompts

  • “/321-frameworks-spring-boot-testing-unit-tests”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • mvn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

321 Frameworks Spring Boot Testing Unit Tests loads about 952 tokens when it runs, and up to ~9.4k if it reads all its reference files. Until then it costs about 218 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~218
When it runs · the whole SKILL.md, loaded when a task matches
~952
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 335 words, ~952 tokens.

Download SKILL.mdSave it as .claude/skills/321-frameworks-spring-boot-testing-unit-tests/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
321-frameworks-spring-boot-testing-unit-tests
description
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
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

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.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/321-frameworks-spring-boot-testing-unit-tests of jabrena/plinth.

  • SKILL.md
  • references/321-frameworks-spring-boot-testing-unit-tests.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

321 Frameworks Spring Boot Testing Unit Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

321 Frameworks Spring Boot Testing Unit Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
321 Frameworks Spring Boot Testing Unit Tests this skilljabrena/plinth446—~952Automated safety check: PassApache-2.0
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-2.0
Java Rulessoftspark/ai-toolkit179—~3.1kAutomated safety check: PassApache-2.0
Spring Data Testingarangodb/spring-data116—~844Automated safety check: PassApache-2.0
Unit Test Config Propertiesgiuseppe-trisciuoglio/developer-kit355—~2.3kAutomated safety check: NotesMIT
Unit Test Exception Handlergiuseppe-trisciuoglio/developer-kit355—~1.6kAutomated safety check: NotesMIT

Similar skills

  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Java Rules

    softspark/ai-toolkit

    Java coding rules: style, patterns, security, testing. An agent skill from softspark/ai-toolkit.

    179 GitHub stars~3.1k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Spring Data Testing

    arangodb/spring-data

    Write and run tests for arangodb/spring-data, select regression coverage, and reproduce CircleCI failures.

    116 GitHub stars~844 tokensUpdated 10 days ago
    Testing & QAAuto-check passed
  • Unit Test Config Properties

    giuseppe-trisciuoglio/developer-kit

    Provides patterns for unit testing @ConfigurationProperties classes with @ConfigurationPropertiesTest.

    355 GitHub stars~2.3k tokensUpdated 28 days ago
    Testing & QAAuto-check: notes
  • Unit Test Exception Handler

    giuseppe-trisciuoglio/developer-kit

    Provides patterns for unit testing @ExceptionHandler and @ControllerAdvice in Spring Boot applications.

    355 GitHub stars~1.6k tokensUpdated 28 days ago
    Testing & QAAuto-check: notes
  • Coverage Check

    AI-Unified-Process/marketplace

    Audits an already-written use case (UC-XXX) or test case (TC-XXX) against its specification and reports a coverage matrix: which main success scenario steps, alternative flows, business rules…

    141 GitHub stars~2.7k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    446 GitHub stars~842 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about 321 Frameworks Spring Boot Testing Unit Tests

What does 321 Frameworks Spring Boot Testing Unit Tests do?

A skill your agent uses 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…. 321 Frameworks Spring Boot Testing Unit Tests is an agent skill from jabrena/plinth.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.

When should I use 321 Frameworks Spring Boot Testing Unit Tests?

321 Frameworks Spring Boot Testing Unit Tests fits situations like: slice tests with @WebMvcTest and @MockitoBean for controllers; @JsonTest for JSON serialization; parameterized tests with @CsvSource/@MethodSource; @TestConfiguration.

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

Run `npx skills add jabrena/plinth --skill 321-frameworks-spring-boot-testing-unit-tests -a claude-code`. Or copy the skill folder (skills/321-frameworks-spring-boot-testing-unit-tests in jabrena/plinth) into .claude/skills/321-frameworks-spring-boot-testing-unit-tests in your project. Claude Code loads it when a task matches its description.

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

Run `npx skills add jabrena/plinth --skill 321-frameworks-spring-boot-testing-unit-tests -a codex`. Or copy the skill folder (skills/321-frameworks-spring-boot-testing-unit-tests in jabrena/plinth) into .agents/skills/321-frameworks-spring-boot-testing-unit-tests in your project. Codex loads it when a task matches its description.

Can I use 321 Frameworks Spring Boot Testing Unit Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 321-frameworks-spring-boot-testing-unit-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/321-frameworks-spring-boot-testing-unit-tests, .gemini/skills/321-frameworks-spring-boot-testing-unit-tests, .github/skills/321-frameworks-spring-boot-testing-unit-tests and .opencode/skills/321-frameworks-spring-boot-testing-unit-tests in your project.

What does 321 Frameworks Spring Boot Testing Unit Tests need to run?

Going by SKILL.md and its folder, 321 Frameworks Spring Boot Testing Unit Tests needs the command-line tools its instructions call (mvn).

Does 321 Frameworks Spring Boot Testing Unit Tests access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 321 Frameworks Spring Boot Testing Unit Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 321 Frameworks Spring Boot Testing Unit Tests use?

321 Frameworks Spring Boot Testing Unit Tests is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 321 Frameworks Spring Boot Testing Unit Tests use?

About 952 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.5k tokens, read only when the agent opens those files.

What are the alternatives to 321 Frameworks Spring Boot Testing Unit Tests?

Skills that share tags, products or a category with 321 Frameworks Spring Boot Testing Unit Tests: Groovy 5 Developer Guide (apache/grails-core, 2.9k stars), Java Rules (softspark/ai-toolkit, 179 stars), Spring Data Testing (arangodb/spring-data, 116 stars) and Unit Test Config Properties (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 321 Frameworks Spring Boot Testing Unit Tests?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.