testing
Use this skill when writing, reviewing, or debugging tests across the codebase. It provides comprehensive testing guidance organized by context, covering CLI, API, web, and Rust applications. The skill emphasizes integration testing at system entry points, mocking only external service boundaries, and testing observable behavior rather than implementation details.
git clone --depth 1 https://github.com/vm0-ai/vm0 /tmp/testing && cp -r /tmp/testing/.claude/skills/testing ~/.claude/skills/testingSKILL.md
# 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) | | Web (`turbo/apps/web`) | [docs/testing.md](../../../docs/testing.md) | [api-testing.md](../../../docs/testing/api-testing.md#migration-from-appsweb) | | 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
Clean Defensive Try-Catch Blocks
Alias for tech-debt issue
Alias for tech-debt research
Patterns and best practices for using ccstate state management in the vm0 platform
Design patterns and conventions for the vm0 CLI user experience
Deep code review and quality analysis for vm0 project
Complete pre-commit workflow - run quality checks (format, lint, type, test) and validate/create conventional commit messages
Database migrations and Drizzle ORM guidelines for the vm0 project