Spring Boot Testing
CheckedGenerates Spring Boot unit & integration tests, including mocks and assertions, based on code context.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add marcelorodrigo/agent-skills --skill spring-boot-testing -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
marcelorodrigo
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned marcelorodrigo/agent-skills at 99d50948fb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 99d50948fb
- Scanned
- 15 files, 2,792 lines
About this skill
What it does
This skill generates Spring Boot 4 unit and integration tests based on your existing code context. It leverages modern testing patterns and best practices, including AssertJ-style assertions for improved readability and MockMvcTester and RestTestClient as alternatives to older approaches. The skill aims to help you write focused and efficient tests by guiding you towards the appropriate test slice for different scenarios (controller, repository, REST client, JSON serialization, or full application).
When to use it
- Testing controller endpoints: When verifying HTTP semantics and controller behavior.
- Validating JPA queries: When ensuring data persistence logic functions correctly.
- Testing interactions with external APIs: When confirming that a REST client integrates properly with external services.
- Verifying JSON serialization/deserialization: When validating the correct mapping of objects to and from JSON format.
- Running full application integration tests: For comprehensive testing of your Spring Boot application.
Key capabilities
- Generates tests using annotations like
@WebMvcTest,@DataJpaTest,@RestClientTest,@JsonTest, and@SpringBootTest. - Supports
MockMvcTesterfor AssertJ-style assertions in web layer tests. - Utilizes
RestTestClientas a modern alternative toTestRestTemplate. - Provides guidance on selecting the appropriate test slice based on the scenario.
- Offers references and documentation for various testing tools including Testcontainers, MockitoBean, and Instancio.
Example prompts
- "Generate a unit test for this controller endpoint."
- "Create an integration test for this repository method."
- "Show me how to test the JSON serialization of this class."
- "What's the best way to test this REST client interaction?"
Tips & gotchas
- The skill is designed for Spring Boot 4 applications. Migration considerations may apply when upgrading from older versions (see
references/sb4-migration.md). - Consider the Test Pyramid principle: prioritize unit tests over integration tests for faster feedback and focused testing.
- If a method or class requires more than 5-7 test cases, it might be too complex and should be refactored.