backend-spring-test

Spring Boot test slice selection depends on the target layer: use @WebMvcTest for controllers, @DataJpaTest for repositories, and full integration tests only when validating cross-layer interactions. Correct slice selection isolates context and prevents excessive mocking.

Slow and brittle Spring Boot tests often stem from overusing full-context bootstrapping and excessive MockBean placement. Replacing broad integration tests with narrower slice annotations improves isolation, reduces context loading overhead, and exposes real defects.

Testcontainers is recommended for repository tests requiring production-accurate database behavior, while H2 suits faster, lighter execution where dialect differences are acceptable. Evaluating database choices ensures test reliability without sacrificing execution speed or isolation.

Fixing Spring test annotation misuse involves evaluating transactional rollback, security context setup, and mock placement to ensure proper context isolation. Applying correct slice annotations prevents unnecessary full-context bootstrapping and stabilizes fragile test setups.

Using MockBean in Spring Boot 3.x tests can mask integration defects and slow context reloading if applied excessively. Limitations include fragile test setup and misleading results when mocking replaces real component interactions within narrow test slices.

Spring test review supports security context and serialization testing scenarios by evaluating slice scope, context reset behavior, and annotation hygiene. It checks whether JSON slices or security-specific setups are applied correctly for robust validation.