tdd-workflow

Topics in the source

• Test-Driven Development Workflow
• When to Activate
• Core Principles
• 1. Tests BEFORE Code
• 2. Coverage Requirements
• 3. Test Types
• Unit Tests
• Integration Tests

This skill ensures all code development follows TDD principles with comprehensive test coverage. Writing new features or functionality Fixing bugs or issues Refactoring existing code Adding API endpoints Creating new components ALWAYS write tests first, then implement code to make tests pass. Minimum 80% coverage (unit + integration + E2E) All edge cases covered Error scenarios tested Boundary conditions verified Individual functions and utilities Component logic Pure functions Helpers and utilities API endpoints Database operations Service interactions External API calls Critical user flows Complete workflows Browser automation UI interactions Do not assume npm test. The commands in the steps and examples below use , , and as placeholders for the project's actual runner. Resolve them once before starting: 1. Run the package-manager detector (ships with ECC): It resolves the package manager (npm / pnpm / yarn / bun) from, in order: CLAUDEPACKAGEMANAGER, .claude/package-manager.json, the package.json packageManager field, the lockfile, then global config. 2. Distinguish the package manager from the test runner — they are not the same. A project can use Bun to install dependencies ye

This is an excerpt. Refer to the complete source and its current requirements.