tdd-workflow

Test-driven development requires writing unit, integration, and end-to-end tests before implementing code. This Skill enforces that workflow and tracks coverage across all test types to reach 80%+ on your codebase, ensuring tests drive design decisions and reduce maintenance burden.

Test-driven development applies to feature development, bug fixes, and refactoring equally. Writing tests first for each change—whether new code, bug resolution, or structural improvement—maintains consistent quality and prevents regressions across your entire workflow.

Unit tests validate individual functions and components in isolation; integration tests verify interactions between modules; end-to-end tests confirm complete user journeys work correctly. TDD requires all three types contributing to your 80%+ coverage target for comprehensive reliability.

A repeatable test workflow integrates with CI pipelines by automating test execution on every code commit. This Skill enforces running your unit, integration, and E2E test suite automatically, validating coverage thresholds are met before code merges and catching failures early.

Falling below 80% coverage indicates untested code paths remain in your codebase. This Skill flags coverage shortfalls, preventing code from progressing until additional tests are written for those paths, maintaining the reliability standard across features, fixes, and refactors.

Test-driven development works with any testing framework—the discipline is writing tests before code, not the tool itself. This Skill enforces the workflow practice and coverage measurement across frameworks; your choice of unit, integration, and E2E testing libraries remains flexible.