test-suite-builder

Avoid full @SpringBootTest usage in Kotlin by generating a minimal, deterministic test suite plan that proves behavior with the smallest footprint. Design tests using slice-level boundaries for controllers, services, and repositories instead of loading the full application context unnecessarily.

Yes, the Kotlin Spring testing approach is coroutine-friendly, utilizing runTest for coroutine testing and preferring MockK over Mockito for mocking. It provides clear guidelines for fixture design to reduce duplication and ensure deterministic test execution.

The best way to test Spring security and serialization boundaries in Kotlin is through slice tests that validate HTTP contracts and security boundaries with minimal, deterministic tests. This avoids overusing mocks and ensures realistic end-to-end workflow validation.

Generate a starter test plan for a Kotlin Spring module by requesting a three-layer strategy covering controllers, services, repositories, security, serialization, and workflows. The output provides sample tests and guidelines for MockK, runTest, and fixture design.

Avoid integration tests for Kotlin Spring applications when unit or slice tests can prove the behavior with a smaller footprint. Reserve integration tests for realistic end-to-end flows, and use slice tests for framework boundaries to prevent unnecessary full-context loading.