Comprehensive testing patterns and anti-patterns for writing and reviewing tests
Scanned 9/2/2026
Install to Claude Code
npx -y skills add vm0-ai/vm0 --skill testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vm0-ai-testing)More formats (shields.io, HTML) on the badges page.
---
name: testing
description: Comprehensive testing patterns and anti-patterns for writing and reviewing tests
context: fork
---
# Testing Skill
Use this skill when writing tests, reviewing test code, or investigating test failures.
## Documentation
Read the testing guide and relevant reference based on context:
| Context | Primary | Reference |
|---------|---------|-----------|
| General | [docs/testing.md](../../../docs/testing.md) | — |
| Anti-patterns | [docs/testing.md](../../../docs/testing.md) | [anti-patterns.md](../../../docs/testing/anti-patterns.md) |
| Patterns | [docs/testing.md](../../../docs/testing.md) | [patterns.md](../../../docs/testing/patterns.md) |
| CLI (`turbo/apps/cli`) | [docs/testing.md](../../../docs/testing.md) | [cli-testing.md](../../../docs/testing/cli-testing.md) |
| CLI E2E (`e2e/tests/`) | [docs/testing.md](../../../docs/testing.md) | [cli-e2e-testing.md](../../../docs/testing/cli-e2e-testing.md) |
| API (`turbo/apps/api`) | [docs/testing.md](../../../docs/testing.md) | [api-testing.md](../../../docs/testing/api-testing.md) |
| App (`turbo/apps/platform`) | [docs/testing.md](../../../docs/testing.md) | [app-testing.md](../../../docs/testing/app-testing.md) |
| Rust (`crates/`) | [docs/testing.md](../../../docs/testing.md) | [rust-testing.md](../../../docs/testing/rust-testing.md) |
| Python addon (`crates/runner/mitm-addon`) | [docs/testing.md](../../../docs/testing.md) | [mitm-addon-testing.md](../../../docs/testing/mitm-addon-testing.md) |
## Key Principles
1. **Integration tests are primary** — test at system entry points
2. **Mock at the boundary** — only mock external services, not internal code
3. **Use real infrastructure** — real database, real filesystem (temp dirs)
4. **Test behavior, not implementation** — verify outcomes, not mock calls
Is this your skill, or is something wrong with this listing? . Author removals are honored within 72 hours.
No comments yet. Be the first to comment!