Testing your Kotlin code helps you catch bugs early. You can use Kotest and MockK to write tests that are clear and easy to understand. This guide shows you how to set up testing patterns for any Kotlin project.
Follow the RED-GREEN-REFACTOR cycle from TDD. First write a test that fails. Then write just enough code to make it pass. Finally improve your code while keeping the tests green. This approach makes your code more reliable.
You also learn about property-based testing and code coverage with Kover. These tools help you find edge cases and ensure your code is well tested. Start writing better tests today.
Global
mkdir -p ~/.claude/skills/kotlin-testingProject
mkdir -p .claude/skills/kotlin-testingSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step