Testing Microservices
summary
Microservices growth slows testing from 3 days to 4 weeks as a fintech expands from two to 80 microservices, forcing adoption of concrete practices: introduced Pact for consumer driven contracts, fortnightly images deployed to six mini-production boxes (300 GB each) to reproduce production, security training for all, swarming teams and a TestOps role, targeted performance on the payments switch, feature flags and signed testing‑in‑production experiments with risk auditors to reduce end‑to‑end surprises.
AI-written summary · about
chapters (20)
- 0:00Introduction and context
- 2:08Engineering environment
- 6:48Evolving testing strategies
- 9:21Microservices challenges
- 17:24Refining the testing process
- 23:18Complexity and strategy
- 24:30Risk beyond boundaries
- 26:44Collaboration and coaching
- 29:17Focusing on customer value
- 29:51Environment management
- 30:37The role of testing tools
- 30:58Production testing and data
- 38:02Swarming for solutions
- 38:18Diversifying test data
- 40:43Building test capabilities
- 41:17Lessons learned in hindsight
- 42:10Ownership and collaboration
- 44:12Quality as an attribute
- 45:04The future of quality
- 49:10Creative testing and conclusion
related talks
57mEnd-to-End Automated Testing in a Microservices Architecture
37mTesting in a Microservices Architecture
47mBreak Up the Monolith: Testing Microservices
45mBuilding a successful test automation architecture in a microservices environment
35mSeven years with microservices: a critical review
24mHow to test microservices and stay sane
27mThe technical journey to microservices
01h 03mMicroservices: Decomposing Applications for Testability and Deployability