TDD as if You Meant It
summary
Demonstrates evolving a working tic-tac-toe engine in short TDD loops using Ruby/RSpec, enforcing three rules: only write production code to make a failing test pass, only create methods by extracting duplication, and only create classes as move-method targets. Uses one failing test at a time cycles of a few minutes to force emergent design rather than upfront design. The team implements state, win detection and refactorings; the engine ends up simpler and test-driven behavior matches expected outcomes.
AI-written summary · about
chapters (7)
- 0:00TDD intro
- 6:23Beck’s TDD cycle
- 8:57Purpose of exercise
- 12:13Live coding rules
- 17:28Tic-tac-toe task
- 22:10First failing test
- 25:29Game states & winner
