Generate Kotest and MockK test patterns with Kover coverage for JVM Kotlin projects.
npx skills add https://github.com/zh667/person-blog --skill kotlin-testing-zh667
Please help me install this Agent Skill. Skill: kotlin-testing Source: https://github.com/zh667/person-blog/tree/main/.cursor/skills/kotlin-testing Command: npx skills add https://github.com/zh667/person-blog --skill kotlin-testing-zh667
Kotlin development often suffers from flaky or brittle tests; this Skill provides patterns using Kotest, MockK, coroutine testing, and property-based testing to produce reliable, maintainable tests.
Create a basic Kotest spec for your Kotlin class, mock dependencies with MockK, and run the test suite with Gradle to verify coverage.
High-intent search queries and answers about installing and using this skill.
Kotlin tests can be structured using Kotest spec styles like StringSpec, FunSpec, BehaviorSpec, and DescribeSpec to provide flexible and readable test layouts. These styles allow you to define test cases hierarchically, adapting the structure to match your specific testing scenarios and module architecture.
MockK integration is the best way to mock dependencies and isolate units in Kotlin testing. It allows you to capture interactions and simulate dependency behavior effectively. By isolating the system under test, MockK ensures your unit tests remain focused, reliable, and free from external side effects.
Property-based testing validates invariants in Kotlin by automatically generating varied inputs to test your code against specified properties. Instead of writing individual test cases, you define the general rules your code must follow. This strengthens correctness by exposing edge cases that traditional example-based tests might miss.
Yes, you need Gradle, Kotlin, and testing libraries like Kotest and MockK to configure and verify Kover coverage thresholds. Kover integrates with your Gradle build to measure code coverage. Configuring these thresholds ensures your test suites maintain the required quality and reliability standards across modules.
Yes, TDD workflow guidance helps fix flaky or brittle Kotlin tests by enforcing the RED-GREEN-REFACTOR cycle to drive implementation. By testing first and refactoring with patterns like MockK and coroutine testing, you produce reliable and maintainable tests that target JVM Kotlin projects without introducing fragility.
windyskyGuide Kotlin 2.0+ development with Ktor, coroutines, and Compose Multiplatform.
satanyakivAnalyze Kover XML coverage reports to prioritize Kotlin test improvements.
himattmDiagnose stuck or leaked Kotlin coroutines in Android apps using DebugProbes.
semicolon-devteamRun Gradle unit, integration, and check tests for Spring Boot Kotlin projects.
