Completed
Passing tests should produce no output
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Effective Unit Testing
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Why do we write unit tests?
- 3 Eliminate everything that makes input or output unclear or contingent
- 4 Why Unit Tests?
- 5 Tests and Thread Safety
- 6 The Two Least Known Facts of Unit Testing
- 7 1. Tests do not share instance data
- 8 2. You can have many test classes per model class.
- 9 Speed
- 10 Passing tests should produce no output
- 11 Failing tests should produce clear output
- 12 Flakiness
- 13 System Skew
- 14 Avoid Conditional Logic in Tests
- 15 Refactoring
- 16 Development Practices
- 17 Final Thoughts
