spring-tdd-mockito

Spring Boot unit testing with Mockito uses annotations like @Mock, @InjectMocks, and @Captor within JUnit 5 test classes. This skill provides ready-to-use test skeleton templates for services, controllers, and repositories to isolate and validate components quickly.

The TDD Red-Green-Refactor cycle is a test-driven development workflow guiding you to write failing tests first, implement code to pass them, and then refactor. This skill applies that cycle to Spring Boot services, controllers, and repositories using Mockito.

Yes, Mockito @Spy annotations along with @Mock and @InjectMocks set up clean test environments for Spring Boot controllers and services. The skill integrates these annotations to facilitate isolated testing and verify interactions.

Spring Boot Mockito unit tests do not need a running database because mocking isolates tested components from external dependencies like repositories. This enables fast feedback by validating service and controller logic without database setup.

Mocking a Spring Boot repository involves using @Mock to simulate the repository and @Captor to capture arguments for verifying interactions. This skill scaffolds these JUnit 5 tests to assert expected behaviors without real database access.