The Grand Unified Theory of Clean Architecture and Test Pyramid
summary
Claims a concrete workflow: build the application core first, write unit tests that run only against that core, then implement tiny translation adapters and verify them with container-backed integration tests (Postgres example), and keep a few smoke tests to validate wiring. Emphasizes packaging by feature (screaming architecture), shrinking exposed surface to avoid accidental contracts, and pruning higher-level tests once a lower-level test reproduces the failure. Key rules include one port at least two adapters, sociable tests, and granular integration tests.
AI-written summary · about
chapters (22)
- 0:00Combining architecture and testing
- 2:13Unified framework for architecture and testing
- 4:20Legacy code to modern architectures
- 7:52Hexagonal and onion architectures
- 11:24Testing pyramid limitations
- 15:54Clean architecture misconceptions
- 19:33Refactoring without proper tests
- 20:34Clean architecture principles
- 22:24Clean architecture flaws
- 26:13Testing with ports and adapters
- 28:45Screaming architecture
- 29:53Tests as host for code
- 31:21Unit tests in application core
- 33:25Unit testing pitfalls
- 36:37Minimizing exposed contracts
- 40:14Integration tests and duplication
- 43:01Granular integration for adapters
- 44:27Wiring and smoke tests
- 45:31Maintaining testing pyramid
- 47:19Step-by-step feature framework
- 50:09Silverlight lessons
- 52:17Summary
related talks
47mThe Grand Unified Theory of Clean Architecture and Test Pyramid
50mThe Grand Unified Theory of Clean Architecture and Test Pyramid
21mTestable Architecture: Keep 'em Separated
30mMastering Testing in a Hexagonal Architecture
20mEffective Testing Approaches for your Application with Cecelia Martinez
06mIgnites - The Test Automation Pyramid
25mTestable Architecture: Keep 'em Separated
51mA testable architecture