Effective Developer Testing: taking it to the next level
summary
Claims that code coverage helps up to about 90% — it correlates with bug detection but is a guide not a goal — and that tests should be prioritized as fast tests rather than debating unit vs E2E. Shows concrete tooling and practices: an IntelliJ prototype called TestNight, a grading engine (ND) with a single run() test API that returns rich results for assertions, and advises hexagonal separation plus observability/controllability. Notes 500 TU Delft students taught, and industry policies for flaky tests (CI auto-delete) to reduce noise.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 7:28Clusters of testing books
- 12:02Systematic testing techniques
- 19:02Code coverage in practice
- 24:00Testing infrastructure importance
- 31:24Test-driven development debate
- 33:33Design for testability rules
- 37:04Handling flaky tests
- 41:15Summary and resources
