Defines best practices for unit and integration testing, emphasizing real runtimes over heavy mocking.
Install
mkdir -p .claude/skills/tests && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9117" && unzip -o skill.zip -d .claude/skills/tests && rm skill.zipInstalls to .claude/skills/tests
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Testing doctrine, commands, and test layout conventionsKey capabilities
- →Enforce directory-based test placement
- →Implement end-to-end integration harnesses
- →Isolate unit tests from external dependencies
- →Configure IPC and UI testing environments
- →Simulate LLM router responses
How it works
It applies standardized folder structures and utilizes predefined test harnesses (IPC/UI/E2E) to categorize and run validation scripts.
Inputs & outputs
When to use tests
- →Structure new integration tests
- →Determine if a module needs unit testing
- →Apply standard mocking conventions
About tests
Enforces testing standards by requiring integration tests for end-to-end coverage and unit tests for isolated, pure logic. It provides rules on where to place tests and how to use LLM routers in a test environment.
Testing doctrine, commands, and test layout conventions
When not to use it
- →Testing unrefined code with high volatility
- →Visual verification that is better served by manual stories
Limitations
- →Restricts mocking to specific router types
- →Cannot bypass the requirement for real runtime tests
How it compares
It enforces architectural discipline regarding where and how code is tested compared to arbitrary test placement.
Compared to similar skills
tests side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tests (this skill) | 0 | 6mo | No flags | Intermediate |
| dependency-upgrade | 26 | 6mo | Review | Intermediate |
| vitest | 41 | 8mo | No flags | Intermediate |
| browser-tools | 6 | 10mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by coder
View all by coder →You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
vitest
antfu
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.
browser-tools
Whamp
Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.