plugins/pokayokay/skills/testing-strategy/SKILL.md
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
npx skillsauth add srstomp/pokayokay testing-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive testing guidance for test architecture, coverage strategy, and test design.
| 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% |
verification-before-completion and cite the fresh command result| Reference | Description | |-----------|-------------| | test-architecture-structure.md | Project structures, shared utilities, test configuration | | test-architecture-isolation.md | Playwright config, database isolation, performance optimization | | test-design-techniques.md | Equivalence partitioning, boundary values, decision tables, state transitions | | test-design-error-and-advanced.md | Error handling tests, property-based testing, parameterization, regression | | frontend-react-testing.md | React Testing Library, queries, user events, hooks, forms | | frontend-vue-a11y-visual.md | Vue Test Utils, accessibility, visual/Storybook testing, anti-patterns | | e2e-playwright.md | Playwright POM, fixtures, auth state, API mocking, visual comparison | | e2e-cypress-and-stability.md | Cypress patterns, flaky test prevention, test data, debugging | | mocking-fundamentals.md | Mock decision tree, stubs/mocks/spies/fakes, MSW setup and usage | | mocking-modules-and-patterns.md | Module mocking, time mocking, anti-patterns, dependency injection | | coverage-guide.md | Coverage metrics, meaningful thresholds, CI integration | | api-test-frameworks-setup.md | Vitest and Jest setup, configuration, running tests | | api-test-supertest-and-helpers.md | Supertest usage, request helpers, custom matchers, snapshots, debugging | | api-integration-patterns.md | CRUD endpoint tests, relationship tests | | api-auth-patterns.md | Login/logout, protected routes, authorization, auth helpers | | api-e2e-and-edge-cases.md | Multi-step workflow tests, error responses, edge cases | | api-test-data-factories.md | Factory patterns, builders, fixtures | | api-test-data-database.md | Database helpers, cleanup strategies, data generation | | api-contract-openapi.md | OpenAPI/AJV schema validation, contract tests | | api-contract-zod-advanced.md | Zod validation, response shape testing, breaking change detection | | api-test-ci-pipelines.md | CI pipeline strategy, GitHub Actions, parallel execution | | api-test-ci-environments.md | Environment config, test reporting, database services, E2E environments | | anti-rationalization.md | Iron Law, common rationalizations, red flag STOP list for TDD discipline |
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when diagnosing bugs, failing tests, build failures, unexpected behavior, flaky tests, regressions, or production incidents. Requires reproduction, root cause evidence, one-hypothesis fixes, and regression verification before editing.