---

name: Testing Test Writing description: Write strategic tests following best practices including minimal tests during development, focus on core user flows only, defer edge case testing until later, test behavior not implementation, use clear descriptive test names, mock external dependencies, and maintain fast execution times. Use this skill when deciding which tests to write during feature development, determining appropriate test coverage levels, writing tests for critical user flows, choosing between unit and integration tests, implementing test mocking strategies, or balancing test coverage with development velocity. This skill applies when working on test files and determining testing strategy for features.

Testing Test Writing

When to use this skill

• When deciding which tests to write during feature development
• When determining appropriate test coverage levels for a feature
• When writing tests for critical user flows and primary workflows
• When choosing between unit tests and integration tests
• When implementing test mocking strategies for external dependencies
• When balancing test coverage with development velocity
• When determining if edge cases should be tested now or later
• When writing clear, descriptive test names that explain intent
• When ensuring tests execute quickly (milliseconds for unit tests)
• When testing behavior and outcomes rather than implementation details
• When working on test files in tests/ directory
• When establishing testing requirements for pull requests

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.

Instructions

For details, refer to the information provided in this file: testing test writing