springboot-tdd
New使用JUnit 5、Mockito、MockMvc、Testcontainers和JaCoCo进行Spring Boot的测试驱动开发。适用于添加功能、修复错误或重构时。
Summary
This skill enables test-driven development for Spring Boot applications using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo.
- It helps developers write robust, well-tested code by generating tests first, ensuring high coverage and reliable refactoring.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "springboot-tdd": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/springboot-tdd Add a new POST endpoint /api/users with fields name and email, following TDD.
Write a unit test for the UserService class that mocks the UserRepository using Mockito.
Create an integration test for the UserController using MockMvc and Testcontainers for PostgreSQL.
Security Audits
Frequently Asked Questions
What is springboot-tdd?
This skill enables test-driven development for Spring Boot applications using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. It helps developers write robust, well-tested code by generating tests first, ensuring high coverage and reliable refactoring.
How to install springboot-tdd?
To install springboot-tdd: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "springboot-tdd": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is springboot-tdd best for?
springboot-tdd is a mcp categorized under Development. It is designed for: testing, coding. Created by affaan-m.
What can I use springboot-tdd for?
springboot-tdd is useful for: When adding a new REST endpoint, generate unit and integration tests before writing the implementation.; When fixing a bug, first write a failing test that reproduces the issue, then implement the fix.; When refactoring existing code, use the skill to ensure all existing tests pass and coverage remains high.; When setting up a new Spring Boot project, quickly scaffold TDD configuration with Testcontainers and JaCoCo.; When verifying database interactions, use Testcontainers to spin up real databases for integration tests.; When improving code quality, run JaCoCo reports to identify untested code paths and add missing tests..