Optimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
summary
Explains how a team halved release lead time from 12 to 6 days by moving service QA responsibilities into the development team and running a focused regression suite of 70 test cases that finish in roughly two hours. Describes a staged 2–3 month migration plan that preserves critical availability checks, uses feature flags to quickly disable problematic features, and reports fewer incidents per year (about 25 → 15).
AI-written summary · about
chapters (11)
- 0:00QA flow optimization intro
- 2:11QA challenges at Cluster
- 7:27Service release QA issues
- 11:46Optimization goals
- 14:37Optimization process steps
- 21:24New QA flow design
- 27:12Transition to new flow
- 30:03Optimization results
- 33:56Change success factors
- 39:40Key takeaways
- 41:31Q&A
related talks
26mHelp! We have a QA problem
40mHelp! We Have a QA Problem!
44mAchieving Excellence in a Startup without a Dedicated QA
21mEstablishing Quality Assurance in Startup environment
23mA little less testing, a little more quality
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
56mNo QA resources? You can still deliver a quality website
45mSame Old Story: Foundation of the QA Department. Tips and Tricks