Kotlin Testing
Kotlin testing patterns: Kotest specs, MockK mocking, coroutine testing, property-based tests, and Kover coverage with TDD discipline.
- What
- Kotlin testing patterns: Kotest specs, MockK mocking, coroutine testing, property-based tests, and Kover coverage with TDD discipline.
- Cost
- Free
- Needs
- Use "Kotlin Testing" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a comprehensive Kotlin testing skill built on Kotest and MockK with real TDD discipline. It walks the full loop: pick the right spec style (StringSpec, FunSpec, BehaviorSpec) for the scope, isolate with MockK including coroutine mocking and argument capture, run red, implement green, refactor, then verify 80%+ coverage with Kover. Property-based testing and Ktor testApplication coverage are included, with runnable examples for each pattern instead of hand-waving. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; assumes a Gradle Kotlin project with Kotest/MockK on the classpath; Kover thresholds are guidance, not law. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Kotlin Testing" with your Muse. Prerequisites: a Gradle-based Kotlin project with Kotest and MockK available. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/kotlin-testing/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review these Kotlin tests against these patterns: spec style choice, MockK isolation, coroutine handling." 3. For new tests, ask: "Write Kotest tests for this class following red-green-refactor, with MockK for dependencies and a Kover check at the end." Tip: match the spec style to the scope; BehaviorSpec for behavior, StringSpec for simple units. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.