TDD is not about writing the test first
summary
Explains why Test-Driven Development means writing tests before production code and how that mindset guides design and development. Covers concrete benefits of writing tests first—forcing conscious problem processing, discovering issues early, removing unnecessary elements, uncovering overlooked requirements, and using test-writing difficulty to judge design viability—and argues that well-practiced TDD reduces waste and delivers economic return on projects.
AI-written summary · about
chapters (18)
- 0:00Introduction to TDD
- 1:04TDD as design guide
- 2:08Explore the problem first
- 4:14Practical example with passwords
- 10:41Focus on what over how
- 12:51Small parts bring calm
- 13:52Business rules in tests
- 15:58Delete unnecessary tests
- 16:40Design and responsibilities
- 18:57Listen to the test
- 26:07Reduced development costs
- 28:54Learning investment
- 31:06Questions on dependencies
- 32:08TDD in legacy code
- 33:55Testing technologies
- 34:17Convincing managers
- 35:42Overcoming bad experiences
- 37:10Standardizing practices
related talks
48mTDD: so your code is testable and tested!
31mTDD: Are you sure about that?
43mTDD: when to use it and, most importantly, when not to
52mThink TDD Doesn't Work? I Have Bad News for You
16mNot Really a TDD Person? Come Discover Canon TDD
01h 13mTDD Revisited
39mTDD Revisited
37mTDD - the why, the how and the when not