About testing-strategies
testing-strategies is a Kotlin testing reference for projects using Micronaut, Retrofit, and MockK. It outlines endpoint and repository coverage, test naming, coroutine mocking, and commands for running tests.
Key features
- 01Integration test guidance for endpoints
- 02Repository test patterns
- 03Test naming and coverage requirements
- 04MockK and coroutine testing rules
- 05Gradle commands for running tests
Use cases
- 01Adding end-to-end tests for an API endpoint
- 02Checking authentication and not-found behavior
- 03Testing repository and coroutine code
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ c0x12c/ ai-toolkit --skill testing-strategiesAfter installing, type/testing-strategiesin Claude Code to confirm it loaded.
Bundled filesexamples.mdintegration-test-setup.md
Details
From the project READMETesting Strategies — Quick Reference
See
integration-test-setup.mdfor @MicronautTest configuration, Retrofit client setup, and connection pool tuning.See
examples.mdfor complete code patterns including MockK, test data builders, and assertions.
Integration Tests
Every endpoint needs an integration test. Extend AbstractControllerTest, use Retrofit clients from module-client, and clean up with truncateAllTables() in @AfterEach.
Key rules:
- Always use Retrofit clients — never raw
HttpRequest - Generate real JWT tokens via
accessToken() - Test full HTTP stack end-to-end, no mocking managers
Test Naming
@Test
fun `{action} - {expected outcome}`() = runBlocking { }
// Examples:
fun `getEmployee - returns employee by id`() = runBlocking { }
fun `getEmployee - returns 404 when not found`() = runBlocking { }
fun `createEmployee - fails with 401 when not authenticated`() = runBlocking { }
Required Test Coverage Per Endpoint
- Happy path — basic success case
- Not found — 404 for missing resource
- Auth failure — 401 without token
- Soft delete — deleted records not returned
@Test
fun `getById - returns 404 when not found`() = runBlocking {
val token = accessToken(prepareUser())
assertThrows<HttpException> {
runBlocking {
client.getById(authorization = token, id = UUID.randomUUID())
}
}.also {
assertThat(it.code()).isEqualTo(404)
}
}
Repository Tests
Extend AbstractRepositoryTest. Every repository needs these tests at minimum:
class DefaultEmployeeRepositoryTest : AbstractRepositoryTest() {
private val repository = DefaultEmployeeRepository(database)
@BeforeEach
fun cleanup() { database.primary.truncateAllTables() }
@Test
fun `insert - happy path`() { }
@Test
fun `byId - returns entity when exists`() { }
@Test
fun `byId - returns null when not exists`() { }
@Test
fun `byId - returns null when soft deleted`() { }
@Test
fun `deleteById - soft deletes entity`() { }
@Test
fun `update - updates selected fields`() { }
}
MockK Rules
mockk<T>()for creating mockscoEvery/coVerifyfor suspend functions (notevery/verify)slot<T>()+capture()to verify what arguments were passedrunTest { }fromkotlinx.coroutines.test— NOTrunBlocking.runTesthandles virtual time and catches coroutine issues.- AAA pattern with comments:
// Given,// When,// Then - Use
@Nested+@DisplayNameto group related tests
See
examples.mdfor full MockK code examples,@Nestedpatterns, test data builders, and AssertJ assertions.
Gotchas
Connection pool exhaustion: If parallel tests fail with "cannot acquire connection", bump maxPoolSize to 20. See integration-test-setup.md for the config snippet.
MockK + coroutines: Always use coEvery/coVerify for suspend functions. Plain every/verify won't work and gives confusing errors.
Run Tests
./gradlew test # All tests
./gradlew test --tests "com.yourcompany.EmployeeControllerTest" # One class
./gradlew :app:module-repository:test # One module