Be lazy — write tests!
summary
The talk argues for writing tests early (TDD-style) rather than adding tests after implementation, showing two concrete task stories: one approached the traditional way without early tests and wasted time, the other used a test-first, 'lazy' approach that saved effort and gave better results. It demonstrates that everything can be tested and promotes adopting test-first practices to be a more efficient developer.
AI-written summary · about
chapters (7)
- 0:00Introduction to TDD
- 3:14Working without tests
- 12:30Writing tests after bugs
- 19:39Extending migration script
- 29:54Automating migration tests
- 33:10Summary
- 38:15Q&A
related talks
40mTDD is not about writing the test first
31mTDD: Are you sure about that?
12mThe Lazy Tester: Musings On Being Efficient
01h 00mTest Last, Test First, TDD: When to Use Each Approach
52mThink TDD Doesn't Work? I Have Bad News for You
46mHow to fall in love with TDD
47mDevelopers Are (Not) Lazy! Why is It So Difficult to Get Programmers to Do Unit Testing
42mUse testing to Develop Better Software Faster