Write awesome tests
summary
Three concrete rules: tests run under one second (plain JVM not emulator, avoid network DB sleeps), tests stay fast, focused, reliable (one assertion per failure, small setup inlined), and tests optimize for failure (inject time/date into a time formatter to avoid flaky timing). Code coverage is meaningless as proof; use CI diff checks instead. Recommend AssertJ style assertions and Mockito-style mocks but avoid nested mocks and spies; practice TDD red‑green‑refactor for incremental, verifiable behavior.
AI-written summary · about
chapters (9)
- 0:00Introduction to awesome tests
- 1:14Why write unit tests
- 3:40Core principles for awesome tests
- 8:13Code coverage myths debunked
- 12:46Test-driven development explained
- 20:35Common testing myths
- 24:55Test code vs production code
- 32:17Tips for better tests
- 39:19Summary and closing
related talks
52m10 simple rules for writing great testcases
48mEffective Unit Testing
40mUnselfish Testing
01h 46mHow Java developers should test their applications (RU)
45mHow to Write Tests in 2021
42mUse testing to Develop Better Software Faster
46mTesting the untestable - patterns and use cases analysis
43mUnselfish Testing