spring-testing

Spring Boot integration tests use Testcontainers to spin up real databases and Kafka, combined with JUnit 5 and AssertJ to verify repository and event handling behavior against live dependencies. This approach ensures repeatable, production-grade test coverage.

MockMvc tests target the controller layer by simulating HTTP requests and asserting API behavior without starting a full server context. This allows fast verification of routing, status codes, and response payloads in a Spring Boot 3.x environment.

Mocking service layer dependencies in Spring Boot unit tests uses Mockito to inject mock implementations, verifying business logic behavior without loading the Spring context. This ensures fast, isolated tests focused on the service class logic.

Yes, this testing approach targets Java 21 and Spring Boot 3.x environments specifically, supporting modern test suites with JUnit 5, AssertJ, Mockito, and Testcontainers. It ensures compatibility with current Spring Boot test slices annotations.

JaCoCo coverage gates in CI enforce minimum test coverage thresholds by analyzing bytecode during the build process. Setting these gates ensures Spring Boot applications maintain reliable unit, integration, and component test coverage before deployment.

Testing Kafka event handling in Spring Boot uses Testcontainers to run a real Kafka broker during integration tests. This verifies event production and consumption logic accurately without relying on mocked message channels.