testing-strategy
Testing Strategy
Comprehensive testing guidance for test architecture, coverage strategy, and test design.
Test Pyramid
| Level | Speed | Cost | Confidence | Share |
|---|---|---|---|---|
| Unit | ~1ms | Low | Narrow | 65-80% |
| Integration | ~100ms | Medium | Medium | 15-25% |
| Contract | ~10ms | Low | API shape | Part of unit |
| E2E | ~1s+ | High | Broad | 5-10% |
Key Principles
- Test behavior, not implementation — test what code does, not how
- For behavior changes, write the failing test first and verify it fails for the expected reason
- Follow the testing pyramid — more unit tests, fewer E2E
- Use meaningful coverage metrics — branch coverage over line coverage
More from srstomp/pokayokay
architecture-review
Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.
301figma-plugin
Use when building Figma plugins, creating design automation tools, implementing sandbox/UI communication, or working with the Figma Plugin API for node manipulation, styles, and components.
79security-audit
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
48sdk-development
Use when building TypeScript SDKs, extracting shared code into packages, creating developer tooling libraries, designing clean API surfaces, or publishing to npm (public or private). Covers typed clients, error handling, multi-target bundling (ESM/CJS/browser).
28session-review
Use after completing work sessions to analyze agent behavior patterns, prepare session handoffs for continuity, document completed work, identify blockers, or preserve context for the next session.
27spike
Time-boxed technical investigation with structured output. Use for feasibility studies, architecture exploration, integration assessment, performance analysis, or risk evaluation. Creates spike tasks in ohno, enforces time-boxing, generates spike reports, and creates actionable follow-up tasks.
25