Deliver Better Code Faster With TDD
summary
Claim: TDD yields higher long‑term throughput despite an initial slowdown (TONTSTAF L) by forcing tiny feedback loops and requirements‑driven tests. Demonstrates building a stack with red‑green‑refactor, using Spock (Groovy) and JUnit style assertions to author executable specifications, walks three concrete scenarios (pop on empty, push/pop single, push/pop multiple), swaps list→array implementation while all tests still pass, and recommends extreme TDD, defect‑driven testing, and coding katas for practice.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:14Refactoring
- 4:25What Makes Tdd Efficient
- 5:05Decouple Design from Implementation
- 5:44Tests Will Fail When Unexpected Changes Occur
- 6:28Common Process versus the Tdd Process
- 12:21Executable Specification
- 13:35How Do I Know What Tests To Write and How Do I Know When I'M Done
- 17:13Spock Testing Framework
- 21:19Refactor
- 21:59Expect Block
- 28:03Tdd in the Real World
- 29:14Practice Writing Unit Specs
- 30:20How Do You Write the Unit Test
- 30:58Defect Driven Testing
- 31:49Summary
