Not Really a TDD Person? Come Discover Canon TDD
summary
Kent Beck’s Canon TDD lays out a specific TDD workflow: start by writing a short list of scenarios, then iterate test-by-test using assertions-first, make each test pass as simply as possible, and refactor only when it produces real design improvement. The talk presents empirical results (TDD can add 15–35% coding time but drastically reduce production defects—Microsoft Visual Studio saw about 90% fewer defects) and reports that practicing this method on real tasks lowers mental load, emphasizes test-ordering as a key skill, and prevents wasted rework.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:18TDD traditional critiques
- 3:20Canon TDD by Kent Beck
- 4:23Writing scenario list
- 6:31Writing effective test
- 7:37Test order and errors
- 9:44Making tests pass
- 10:27Refactoring step
- 11:32Loop until boredom
- 12:56Q&A
related talks
49mESSENTIALS - Canon Test-Driven Development
43mTDD — Things I Learned in the Last 12 Years
42mTo TDD or not to TDD: that is the question!
52mThink TDD Doesn't Work? I Have Bad News for You
28mTDD for Absolute Beginners
48mTDD - It's About More Than Just the Tests
37mTDD - the why, the how and the when not
53mHow to fall in love with TDD