End-to-End Test Architectures, a Dead End Road
summary
Argues that full end-to-end “production-like” pre-prod environments are costly, fragile and slow for distributed DevOps, and should be replaced by consumer-driven contract tests between services, fast isolated unit and integration tests per component, and progressive release patterns such as canary and blue‑green deployments with feature toggles, supported by monitoring and rollback to maintain safety while avoiding brittle shared E2E labs.
AI-written summary · about
chapters (15)
- 0:00End-to-end testing challenges
- 2:07Spaghetti banking systems
- 6:47Finance teams resist DevOps
- 10:04Test environment problems
- 12:58Integration testing across teams
- 17:23Five years at Rabobank
- 22:05Management’s role in failures
- 25:41Manual testing illusion
- 29:02Teams breaking each other’s code
- 31:10End-to-end testing dead end
- 34:03Contract testing alternative
- 37:17Safe production testing
- 40:25Canary deployment risks
- 42:10Future of independent testing
- 42:53Q&A
related talks
11mDeath to Test Environments
41mEnd-2-end testing without the pain
01h 02mThe Art & Joy of Testing in Production
54mSurviving the Underworld of End-to-End Tests
57mEnd-to-End Automated Testing in a Microservices Architecture
45mBuilding a successful test automation architecture in a microservices environment
44mContinuous Performance Testing in DevOps
37mThe Journey of End-to-End Automated Testing