Adapting Test Strategies to Modern Deployment Methods
summary
More than 50% of deployment failures trace to weak test strategy, so the team moves to blue-green deployment and adds canary 20% rollout and feature-flag workflows, backed by containerization and orchestration (Docker / Kubernetes) so testers can spin up test environments on demand. A 120-person survey shows 63% were uninvolved and 52% felt left behind. Outcome: weekday deploys succeed, performance testing and DB migration tests are added after an initial DB-change failure, and monitoring dashboards surface real user impacts within six months.
AI-written summary · about
chapters (9)
- 0:00Modern test strategy challenges
- 4:39Traditional to modern deployment
- 6:48Why blue-green deployment
- 8:55Team change management
- 11:18Test engineering impacts
- 14:27Cloud-native tools for testers
- 16:54Team structure evolution
- 19:23Future of test strategy
- 20:06Q&A on database changes
related talks
40mSowmya Sridharamurthy: Adapting Test Strategies to Modern Deployment Methods
49mThe Whole Team Approach to Testing in Continuous Delivery
53mTransforming testing methodologies: From manual to robust strategies
32mHow Your Deployment Strategy Influences How People Code
57mOptimizing Your Testing Team
44mI Deploy On Fridays
22mTesting in Production
37mUnderstanding the successes and the pain points of different testing strategies
