← ClaudeAtlas

test-patternslisted

Testing conventions covering test design, fixtures, mocking, query priority, async handling, behavior-vs-implementation tests, boundary coverage, and what to skip. Use whenever the project contains test config files (e.g. `vitest.config.*`, `jest.config.*`, `playwright.config.*`, `pytest.ini`, `conftest.py`) or test directories (`tests/`, `__tests__/`, `spec/`), OR the user asks about tests, testing, unit tests, integration tests, e2e tests, mocking, fixtures, coverage, test failures, or extending test coverage in any stack, even if a specific framework is not mentioned by name.
ku5ic/dotfiles · ★ 0 · Testing & QA · score 72
Install: claude install-skill ku5ic/dotfiles
# Test patterns Apply the runner-specific reference matching the detected test runner. Principles apply to all stacks. ## Severity rubric - `failure`: a concrete defect or violation that should not ship. - `warning`: a smell or pattern that compounds with other findings. - `info`: a hardening opportunity or note, not a defect. ## Reference files | File | Covers | | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- | | [reference/anti-patterns.md](reference/anti-patterns.md) | Severity-labeled anti-patterns: implementation details, async pitfalls, mock abuse | | [reference/principles.md](reference/principles.md) | Test design principles + Test Pyramid (Fowler) vs Testing Trophy (Dodds) | | [reference/vitest-and-jest.md](reference/vitest-and-jest.md) | Shared Jest / Vitest patterns, runner choice, MSW for HTTP mocking | | [reference/react-testing-library.md](reference/react-testing-library.md) | Query priority, full priority order, `getBy` vs `queryBy` vs `findBy` semantics | | [reference/playwright.md](reference/playwright.md) | Playwright patterns, page object, property-based testing (fast-check, hypothesis) | | [reference/