The Little Shop of TDD Horrors
summary
This talk examines misuse of Test-Driven Development (TDD) and how bad tests — "testing smells" — harm design and architecture in web and mobile applications. It identifies common problematic test patterns and shows how to avoid them, using real-world examples in JavaScript, Swift, and Java for Android.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:07What is TDD and why use it
- 4:42Test setup horrors
- 6:09Minimal tests real value
- 7:56Iteration refactoring with TDD
- 9:00Readable test descriptions
- 11:29Testing private methods reflection
- 12:32Edge cases unhandled input
- 14:22Repetitive tests automation
- 15:52Clear test descriptions
- 18:03Descriptive test names
- 20:14Ambiguity conditional behavior
- 21:42TDD for bug handling
- 22:46Testing network interactions
- 24:58Stubs mocks for performance
- 26:44Testing behavior vs methods
- 28:08TDD developer value
- 28:52Team collaboration
- 30:17Test complexity refactoring
- 31:44Automated tests video bugs
- 33:09UI testing pixels layout
- 34:13Early QA integration
- 35:17Ultimate test purpose
- 37:06Maintainability fear of code
- 38:34Tests as documentation clarity
- 40:44Pair programming perspectives
- 41:53Tests as source code
- 42:59Q&A
