The Grand Unified Theory of Clean Architecture and Test Pyramid
summary
Claims a practical framework: start in the core and write sociable unit tests around the domain, reduce public surface and avoid overmocking; delay delivery‑mechanism choices and implement adapters only after the core is stable; delay adapter decisions and test adapters against ports with real containers by spinning up Docker/testcontainers and exercising the adapter contract against a real database or message broker; finish with lightweight application smoke tests to validate wiring and DI in a .NET API.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 3:57Personal journey
- 8:33Hexagonal architecture
- 13:49Testing pyramid challenges
- 15:59Clean architecture flaws
- 20:17Core principles
- 23:52Redesigning architecture
- 27:50Testing importance
- 29:15Reconciling architecture and testing
- 30:20Unit tests pitfalls
- 31:45Solitary vs sociable testing
- 35:57Integration tests
- 39:28Application tests
- 40:33Maintaining pyramid
- 43:20Final framework
- 45:07Historical lessons
related talks
50mThe Grand Unified Theory of Clean Architecture and Test Pyramid
53mThe Grand Unified Theory of Clean Architecture and Test Pyramid
30mMastering Testing in a Hexagonal Architecture
25mTestable Architecture: Keep 'em Separated
21mTestable Architecture: Keep 'em Separated
51mA testable architecture
46mThe Road to Improving Testability
43mTest Driven Design - Coupling Loosely