Test, Transform, Refactor
summary
Concrete claim: disciplined Red-Green-Refactor plus a prioritized set of micro-changes — transformation priority — reveals algorithms without big rabbit‑hole rewrites. Demonstration uses PHPSpec (Prophecy) and PHPUnit, a 20‑minute kata timebox, ping‑pong pairing and a walking‑skeleton approach. The Roman‑numerals kata gets built incrementally: null→constant→if→loop→generic and ends green and working. Advice: write tests for new work, refactor when tests make it hard, and prefer small, ordered transformations.
AI-written summary · about
chapters (5)
- 0:00Start
- 11:01The Roman Numerals Kata
- 24:02Walking skeleton
- 25:41Transformation null - constant
- 26:48Transformation statement - statements
related talks
40mTesting Legacy Code: Safe Refactoring
43mFrom 0% to Cleanly Refactored 100% tested code
28mTDD for Absolute Beginners
45mTesting Legacy Code - What To Do When It Seems Untestable
35mRefactoring Frenzy - Don't settle for short term
01h 03mRewiring your brain with test driven thinking in C++
41mTesting Legacy Code & Safe Refactoring
50mHello my name is "if"
