Test Suite Builder
Design and generate layered Kotlin + Spring tests that balance speed, realism, and regression value across unit, slice, and integration levels. Use when adding coverage for business logic, controllers, repositories, security, serialization, or end-to-end workflows, and when generic AI output would otherwise overuse `@SpringBootTest`, misuse mocks, or ignore MockK and coroutine testing idioms.
Install
npx skills add JetBrains/skills --skill test-suite-buildergit clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/test-suite-builder ~/.claude/skills/test-suite-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Suite Builder Source mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-14`). ## Mission Choose the lightest test that proves the behavior. Generate tests that catch regressions instead of reproducing the implementation line by line. ## Start With A Test Strategy Before writing code, classify what needs to be proven: - pure business logic - HTTP contract and validation - repository query behavior - serialization behavior - security rules - cross-component integration - database or message-broker integration ## Three-Layer Strategy - Use unit tests for domain logic, calculations, decision tables, and deterministic branching. - Use slice tests for framework boundaries: - `@WebMvcTest` or `WebTestClient` for HTTP - `@DataJpaTest` for repositories - focused JSON or security slices when available in the project - Use `@SpringBootTest` and Testcontainers only when a realistic application graph or infrastructure boundary must be proven. ## Kotlin Testing Rules - Prefer JUnit 5. - Prefer MockK over Mockito unless the repository already standardizes on something else. - Use readable backtick test names when that matches the project style. - Use `runTest` and the coroutine test toolkit for coroutine-heavy code. - Build reusable fixtures, builders, or object mothers instead of duplicating inline object construction. ## What To Cover - Success path. - Validation failures. - Business rule failures.
Details
- Skill name
test-suite-builder- Repository
- JetBrains/skills
- Path
test-suite-builder/SKILL.md- Repo updated
- 21 October 2026
FAQ
What does the Test Suite Builder skill do?
Design and generate layered Kotlin + Spring tests that balance speed, realism, and regression value across unit, slice, and integration levels. Use when adding coverage for business logic, controllers, repositories, security, serialization, or end-to-end workflows, and when generic AI output would otherwise overuse `@SpringBootTest`, misuse mocks, or ignore MockK and coroutine testing idioms.
How do I install the Test Suite Builder skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill test-suite-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Suite Builder popular?
It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.
Related skills
Deploy to Vercel
398JetBrains/skills
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Vercel React Native Skills
398JetBrains/skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Vitest
398JetBrains/skills
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Reality Testing Decisions
190apple-ouyang/book-to-skill
Use when tempted to predict, analyze, or debate whether something will work instead of testing it. When facing uncertainty about a decision, product, hire, or opportunity and relying on gut feeling or expert opinions.
Skillshare Implement Feature
398JetBrains/skills
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development, proper handler split conventions, oplog instrumentation, and dual-mode (global/project) patterns. If the request involves writing Go code and tests, use this skill — even if the user doesn't explicitly say "implement".
Skill Forge Benchmark
189AgriciDaniel/skill-forge
Benchmark Claude Code skill performance with variance analysis, tracking pass rate, execution time, and token usage across iterations. Runs multiple trials per eval for statistical reliability, aggregates results into benchmark.json, and generates comparison reports between skill versions. Use when user says "benchmark skill", "measure skill performance", "skill metrics", "compare skill versions", "skill performance", "track skill improvement", "skill regression test", or "skill A/B test".
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.