You don’t need unit tests!
summary
Argues that high unit-test coverage and many unit tests do not guarantee code quality or safety, and demonstrates where relying solely on unit tests creates a false sense of security. Explains distinctions between test coverage and actual software quality, and presents alternative practices or approaches to improve safety beyond unit testing.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:14Unit tests - what we will gain?
- 11:55Documentation? Or implementation?
- 16:44What you have to understand to understand tests?
- 19:50Too much is too much...
- 23:27Do you really feel safe?
- 26:48Assumptions may change...
- 30:42TDD-be lazy in a good way
- 32:30Component Tests!
- 33:14Boundaries
- 34:03Don't Mock everything!
related talks
28mUnveiling the Illusion: Why Coverage Alone Is Misleading
03mTest coverage
55mThe Science of Unit Tests
07mHow code coverage can be used and abused to guide testing.
01h 48mNo Such Thing as Manual Testing and Other Confusions
39mTen things you heard about testing that might be wrong
37mClean Test Code
47mThe secret unit testing tools no one ever told you about