test-patterns

Run unit tests with ./gradlew test and integration tests with ./gradlew integrationTest. Both commands execute the appropriate test suites defined in your Gradle build, discovering and running tests across your Kotlin/Spring Boot project structure.

WebTestClient provides a non-blocking HTTP client for testing reactive Spring WebFlux endpoints in Kotlin. Use it to test async request/response flows, validate status codes and response bodies, and verify reactive stream behavior in integration tests.

Run ./gradlew check to execute all tests and generate coverage reports. Review the JaCoCo HTML reports to analyze coverage totals, identify gaps in your unit and integration tests, and track coverage metrics across test suites.

Yes, MockK is a Kotlin-native mocking library designed for Kotlin unit tests. It integrates with Spring Boot test frameworks to mock dependencies, verify interactions, and stub return values in your Kotlin test suite.

Acceptance tests validate end-to-end workflows using WebTestClient or HTTP clients to exercise full Spring Boot application flows. Organize them separately from unit tests, use realistic test data, and verify complete user journeys and API contracts.

Unit tests validate individual Kotlin functions in isolation using mocks. Integration tests verify component interactions within Spring Boot context. Acceptance tests confirm end-to-end workflows through the full application stack.