Test-Driven Development for coding and bug fixing. cycle - Red→Green→Refactor cycle, defining expected behavior, bug-fix TDD, anti-patterns [cycle.md], run - test execution workflow (environment detection→impact scope→execution→result reporting) [run.md], test-strategies - boundary value·equivalence partitioning·decision table·error guessing·path coverage test design techniques [test-strategies.md]. "TDD", "test first", "failing test", "doesn't work", "not working", "test design", "boundary value test", "test strategies", "equivalence partitioning", "bug fix", "run tests", "execute tests", "test run", "verify" triggers

Install

openclaw skills install tdd

TDD (Test-Driven Development)

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

Topics

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

Quick Reference

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.