Reversed Test Pyramid — Dealing with Legacy Code
summary
Reversed Tests Pyramid explains how to approach large, untestable legacy codebases by flipping the usual testing pyramid: instead of mostly unit tests, start with more automated end-to-end and integration tests (including GUI and database tests) to gain safety and understanding. It covers practical practices and techniques for introducing these higher-level tests to protect unpredictable, multi-developer systems where refactoring to a clean, testable architecture isn’t immediately possible.
AI-written summary · about
chapters (11)
- 0:00Reversed test pyramid intro
- 6:03Legacy code testing
- 7:29Who creates legacy code
- 9:14Technical debt impact
- 14:32Handling legacy code
- 21:33When to take tech debt
- 24:19Paying down tech debt
- 27:11Rewriting systems rarely works
- 30:04Maintaining end-to-end tests
- 32:36Estimating tech debt size
- 34:43Summary & Q&A
related talks
17mYet again an upside down test pyramid – what can we do about it?
48mBreaking free from the Test Pyramid
35mDemystifying the test pyramid
09mInvert the Pyramid Testing
46mThe Refactoring Pyramid
46mThe Secrets of the Pyramids
45mTesting Legacy Code - What To Do When It Seems Untestable
53mThe Grand Unified Theory of Clean Architecture and Test Pyramid