Inverting Test Pyramid - A First Hand Experience Report
summary
Started with ~50% UI automation over two years and ~5–10% unit/service coverage, then flips testing to focus on fast unit and domain-logic tests plus targeted integration tests and minimal UI checks. Built class-level business tests (example: 17 scenarios run in ~17s on CI) and introduced Cucumber-style acceptance and CI runs. Result: UI suite drops from ~14 hours to ~10 minutes, backend tests run 7–10x faster, and production defects fall from ~7–8 down to ~1 per release.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:20Agenda
- 3:50Release Cycle
- 6:10Data Validation
- 7:55Regression Testing
- 14:20Demo
- 18:20Automation
- 20:15Problems with this approach
- 22:40Maintenance
- 24:40Data Analysis
- 26:20Inverting Test Pyramid
- 29:45Workflows
- 31:50System Tests
- 35:50Biggest Hurdle
- 45:35Building Teams Capability
- 48:40Categorization
- 50:30Development Time
- 53:05Unit Test Coverage
related talks
09mInvert the Pyramid Testing
56mThe End Game
22mTwo years of UI Testing
17mYet again an upside down test pyramid – what can we do about it?
06mIgnites - The Test Automation Pyramid
38mScaling Automated Testing & Architecture from Startup to Enterprise
20mThe Road to Continuous Testing
21mLowering End to End Testing Barriers