TDD (Test-Driven Development)#

Test-Driven Development: define expected behavior first, then make it pass with implementation.

Topics#

TopicDescriptionGuidecycleRed→Green→Refactor cycle, bug-fix TDD, anti-patternscycle.mdrunTest execution workflow (environment detection→impact scope→execution→result reporting)run.mdtest-strategiesBoundary value·equivalence partitioning·decision table·error guessing·path coveragetest-strategies.md

Quick Reference#

Trigger entry (HARD STOP — first action)#

When this skill is invoked, the FIRST tool call must be TaskCreate (Red/Green/Refactor/Verify) + Red test authoring. Diagnosis, planning, option asks, and medium decisions are forbidden before Red is authored + executed + failure confirmed. See cycle.md "Trigger entry".

TDD Cycle#

Define expected behavior → natural failure → implement → pass → refactor. See cycle.md.

Test Execution#

Environment detection → impact scope → execution (unit→integration→e2e) → result reporting. See run.md.

Test Design Techniques#

Decide which test cases to write (boundary value, equivalence partitioning, etc.). See test-strategies.md.