spring-testing

Structure Spring Boot tests by applying module-oriented strategies: unit tests with MockK for domain, integration tests with Testcontainers for infra, and slice tests with @WebMvcTest for app-api. This ensures reliable testing across isolated modules and maintainable test infrastructure.

Set up Testcontainers for Spring Boot integration tests by defining reusable configurations within the infra module. This approach provides isolated, disposable database environments for integration testing, ensuring reliable execution without manual container management.

Yes, you can use MockK with @WebMvcTest to test Spring Boot REST controllers in the app-api module. This combination slices the web layer for focused controller testing and integrates with REST Docs to generate API documentation from your test cases.

Create reusable test data fixtures for Kotlin domain models using the Object Mother pattern. This pattern centralizes test data construction, ensuring consistent domain object creation across unit tests while maintaining isolation and reducing test setup duplication.

Yes, this testing pattern supports @DataJpaTest for repository slices within the infra module. It provides comprehensive testing patterns that include repository slice testing and anti-pattern awareness to keep database tests isolated and maintainable.

Avoiding anti-patterns in Spring Boot slice tests prevents cross-module dependencies from leaking into isolated test contexts. The Skill defines anti-pattern awareness to keep tests maintainable, ensuring @WebMvcTest and @DataJpaTest slices remain fast and focused.