testing-writing-guidelines

name

Testing Writing Guidelines

description

Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked external dependencies, and fast execution, deferring edge case testing until explicitly required. Use this skill when creating or modifying test files, writing unit tests, integration tests, or test cases for any feature. Apply when writing test files (test/, __tests__/, spec/, .test.js, .spec.ts, test_*.py), implementing tests for core user workflows, testing critical business logic, mocking external dependencies (databases, APIs, file systems), writing descriptive test names, creating fast-running unit tests, or adding tests at logical completion points of feature development. Use for any task involving test creation, test coverage, test strategy, or test-driven development.

Testing Writing Guidelines

Core Philosophy: Write minimal, focused tests for critical paths. Defer comprehensive testing until explicitly requested.

When to use this skill

• When creating or modifying test files (test/, tests/, *.test.js, .spec.ts, test_.py)
• When writing unit tests for core business logic and critical user workflows
• When implementing integration tests at logical feature completion points
• When writing test names that clearly describe what is being tested and expected outcome
• When mocking external dependencies like databases, APIs, or file systems to isolate units
• When focusing tests on behavior (what the code does) rather than implementation details
• When ensuring unit tests execute quickly (milliseconds) for frequent developer runs
• When testing core user flows and primary workflows (deferring edge cases unless critical)
• When writing minimal tests during feature development, focusing on main functionality
• When avoiding excessive testing of non-critical utilities or secondary workflows
• When deciding test coverage strategy for new features or refactoring

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle testing test writing.