The Road to Improving Testability
summary
Claims that refactoring to clean architecture / ports and adapters reduces coupling and makes the business core fast to unit test, that a three‑way tradeoff exists between speed, signal (low noise) and protection, and that isolating algorithms from coordination lets unit, integration and end‑to‑end tests sit where they give most value. Recommends SonarQube and git hot‑spot analysis, warns against overmocking, cites peppy.health as the practical destination and gives the surprising Autobahn upkeep figure €800,000 per mile per year.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 5:53Moving fast safely
- 10:12Traditional layered architecture
- 13:43Clean architecture
- 15:09Endless refactoring cycle
- 17:15High-value tests
- 20:02Low-value tests and tech debt
- 23:33Test confidence signal vs noise
- 26:01Test speed vs refactorability
- 29:08Code complexity mapping
- 33:41Untestable code danger
- 36:28Road to improving testability
- 37:51Question and answer session
related talks
49mDesign for Test
20mThe Art of Testing
53mThe Grand Unified Theory of Clean Architecture and Test Pyramid
46mTesting the untestable - patterns and use cases analysis
47mThe Grand Unified Theory of Clean Architecture and Test Pyramid
51mA testable architecture
40mTesting Software Architecture
42mUse testing to Develop Better Software Faster