Skip to main content
skill CX Codex

testing-strategies · c0x12c — Claude Code skill for Micronaut/Kotlin tests

Gives your coding agent ready test patterns for a Micronaut and Kotlin backend: integration tests, repository tests, test data builders.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add c0x12c/ai-toolkit --skill testing-strategies -a claude-code
Open on GitHub

What testing-strategies does

This skill spells out how tests should look in a Micronaut and Kotlin project. Every endpoint gets an integration test that extends AbstractControllerTest, calls Retrofit clients from module-client, and wipes the database with truncateAllTables() inside @AfterEach. Raw HttpRequest is off the table. Tokens come from accessToken(), managers stay unmocked, and the whole HTTP stack runs end to end.

Repositories follow their own template. Tests extend AbstractRepositoryTest and cover at least insert, lookup by id, a missing row, a soft-deleted row, and a partial update. The MockK section is blunt about coroutines: use coEvery and coVerify for suspend functions, never every and verify, and reach for runTest from kotlinx.coroutines.test instead of runBlocking. Plain every on a suspend function fails with a confusing error, so this rule saves debugging time.

Parallel runs get a note too: when tests die with a connection-acquisition error, raise maxPoolSize to 20. Configuration for @MicronautTest and the clients lives in integration-test-setup.md; full code samples with MockK and AssertJ are in examples.md. Tests run through Gradle — the whole suite, a single class, or one module.

What it helps with

  • write an integration test for a new endpoint
  • cover a repository with the baseline set of checks
  • figure out why MockK misses a suspend function
  • fix parallel tests failing on connection pool exhaustion
  • build test fixtures with data builders

Example prompts for the agent

  • Write an integration test for the get-employee-by-id endpoint
  • Add repository tests for DefaultEmployeeRepository, including soft delete
  • Check that suspend functions in the tests use coEvery and coVerify

How to install testing-strategies

1Skills CLI (Vercel)

npx skills add c0x12c/ai-toolkit --skill testing-strategies -a claude-code

2Manually: put the files in place

~/.claude/skills/testing-strategies/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/testing-strategies/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about testing-strategies

How do I install testing-strategies in Claude Code?

Run npx skills add c0x12c/ai-toolkit --skill testing-strategies -a claude-code. The skill lands in ~/.claude/skills/testing-strategies/SKILL.md.

What does testing-strategies do?

It hands the agent test patterns for a Micronaut and Kotlin backend: integration tests over Retrofit clients, repository tests, MockK rules, and test data builders.

Which tools can the skill use?

Read, Write, Edit, Glob, Grep and Bash, so the agent can inspect code, edit files, and run tests through Gradle.

Similar skills

All skills for Testing and QA →

testing-strategies by other authors comes first.

From the same set11

terraform-review Walks Terraform changes through an 8-category checklist and returns a verdict: Approved, Needs Changes or Blocked. Useful before merging an infrastructure PR. CX Codex +1 ★ 109repo stars startup-pipeline Moves a startup idea through four stages: brainstorm, validation, market research and pitch materials. Gates between stages stop weak ideas early. CX Codex +1 ★ 109repo stars python-testing-strategies A skill that tells your coding agent how to test FastAPI apps: pytest-asyncio, httpx AsyncClient, data factories and the checks every endpoint needs. CX Codex +1 ★ 109repo stars ops-oncall-log Pulls alerts from your monitoring platform and writes a structured on-call log to the team wiki. Useful at the end of a shift or during a review. CX Codex +1 ★ 109repo stars kotlin-best-practices A skill that pins down Kotlin conventions: null safety, Either instead of thrown exceptions, coroutines, and Exposed ORM patterns. Useful while writing or reviewing Kotlin. CX Codex +1 ★ 109repo stars investor-materials A skill for producing investor-facing documents: a pitch deck, one-pager, memo and financial model. Useful when the numbers and the story have to line up across every file. CX Codex +1 ★ 109repo stars design-intelligence Bootstraps a design system from scratch: palette, type scale, spacing, radii and a component inventory in three formats. CX Codex +1 ★ 109repo stars database-patterns Hands your agent a fixed set of database rules: column types, UUID keys, soft deletes and migration templates. Useful when it writes tables or repositories. CX Codex +1 ★ 109repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor