Test to Break Principles
summary
Live coding demo shows TDD moving from “test to work” to test to break with concrete code: an email validator built by iterating tests, simple regex, PHPUnit asserts, then adding exception checks so orders with blue color or three or five wheels throw errors. Three failing tests become green after guarding logic, demonstrating the actual tools (PHPUnit, annotations), the surprising bugs found, and how tests force code that only works one way.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:18Hit the Tree?!
- 3:463 Types of Test
- 6:54Does the system work as expected with standard inputs?
- 19:58The Working Software Myth
- 20:56Trabant 1957
- 22:13Reliant Robin 1973
- 23:53Good software functions well and is bug free.
- 31:43Complexity is standard
- 32:40Code Example
related talks
52mWriting Unit Tests Using PHPUnit
01h 04mTest Driven Development with C# - from Padawan to Jedi
10mWrite Better Tests With TDD
12mTesting: What's it all about?
49mESSENTIALS - Canon Test-Driven Development
01h 05mTDD and The Terminator — An Introduction to Test Driven Development
28mTDD for Absolute Beginners
46mHow to fall in love with TDD