backend-testing

Spring Boot backend tests are structured under src/test/java using JUnit5 and MockMvc. Apply a conventional test package layout with clear naming conventions to organize unit, service, controller, and integration tests for maintainability.

Use @MockitoBean and @MockitoSpyBean instead of @MockBean and @SpyBean to isolate dependencies in Spring Boot tests. This approach enforces modern Mockito-based isolation, ensuring reliable mock injection and avoiding deprecated annotation behaviors in your testing guidelines.

Yes, generate API documentation from MockMvc controller tests using Spring REST Docs. This captures actual API behavior during test execution, producing accurate and maintainable documentation directly from your structured Spring Boot test verifications.

Write integration tests for Spring Boot REST endpoints using Spring Boot Test with MockMvc. This provides structured verification of request and response payloads while maintaining consistent testing conventions across controller and service layers.

This testing convention primarily targets Spring Boot applications using JUnit5 and Spring Boot Test. While the basic unit testing guidelines and Mockito isolation practices may apply to general Java projects, the MockMvc and Spring REST Docs integration specifically requires the Spring Boot framework context.