Test-Driven Repair
summary
Assigning tests to a 3,000-line enterprise Java mess, the concrete workflow is: pick an interface you can invoke, wrap it in JUnit or WebDriver or call the executable as a subprocess, add data-driven parametric tests rather than bespoke test functions, measure branch coverage (a 26-line example needs five tests for full branch coverage), cluster tests to avoid repeated setup, run nightly full-sanitization suites, and refactor toward a functional-core/imperative-shell so fast pure functions get unit tests and the slow IO stays in a few integration tests.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:24Test-Driven Development
- 6:03Structured Testing
- 6:41Why write tests early?
- 11:48Test Coverings
- 13:07Interfaces for testing
- 17:45Interface test invariants
related talks
51mTest-Driven: from Zero to Hero
48mMake your tests tell the story of your domain
01h 02mThe Unit Tests Strike Back: Testing the Hard Parts
41mFixing Design with Tests
40mIntegration Testing from the Trenches - Rebooted
05mTaming the Testing Beast
02h 58mOverview of Testing in Our Applications
54mDirty Tests And How To Clean Them