Got a #bug? Your Unit Tests Are Not Properly Designed
summary
Explains why many teams fail to get value from automated testing by focusing on how to design good unit tests. Covers the testing pyramid (end-to-end, integration, unit) and gives visual examples, metrics and references showing how properly written unit tests improve internal code quality, external product quality, and deliver a sustainable ROI for test automation.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 9:33What is a unit in testing?
- 15:14Unit test strategy
- 25:12Behavior vs collaboration tests
- 30:34Builder pattern in unit tests
- 34:16Testing as creative process
- 35:59Q&A
related talks
32mAchieving a Shared Understanding of Unit Tests
39mThe Good Testing, The Bad Testing and The Ugly Testing
40mA Tale of Unit Tests, Code Coverage and Code Design
01h 48mNo Such Thing as Manual Testing and Other Confusions
39mTen things you heard about testing that might be wrong
55mUnit Testing Like a Pro - Towards a Testable Design
51mChecking Unit Tests: Key Signs of Failing Approaches
48mBreaking free from the Test Pyramid