Testing TDD

Overview

Use this skill to drive implementation through fast red-green-refactor cycles with explicit design feedback.

Scope Boundaries

• Use when implementation should be guided by failing tests first.
• Typical requests:
  • Develop a new feature with strict red-green-refactor discipline.
  • Reduce refactor risk with micro-cycle verification.
  • Use tests to shape API and domain design incrementally.
• Do not use when:
  • Tests are added only after full implementation.
  • The primary goal is performance/load experimentation.

Inputs

• Target behavior and constraints
• Existing test harness and coding standards
• Cycle-time and commit-granularity expectations