What Happens When Everyone is QA? And I Mean Everyone!
summary
Claims concrete results: Top 25 app by comScore, 4.5 stars from ~1M reviews, and faster shipping with fewer bugs after making everyone part of QA. Specifics: require unit/UI tests before merge, CI gates, developer first-pass smoke tests, automated test environments and fixtures, a catfood build with ~8,000 weekly users and ~200 feedbacks per release (TestFairy, crashlytics/Fabric, Splunk), automated JIRA ticketing from feedback, A/B rollouts starting at 5%. The system ships, finds device- and region-specific bugs, and measurably improves quality.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:35Why QA
- 3:20What does everyone mean
- 5:07Continuous Integration
- 9:50Developers
- 12:40Dev First Pass
- 15:45QA
- 31:28Developer First Pass
- 36:35How to Get Feedback
- 37:35Unit Tests
- 38:40QA QA QA QA
- 40:42QA QA QA
- 42:12Devices
- 43:42QA for Developers
- 46:57User Reviews
related talks
39mHow To Elevate QA In Your Organization
43mLean QA: Automation, Monitoring, Experiments
36mWhy a Growing Company Needs a Growing QA Team
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
53mIs having a QA a symptom of a dysfunctional team?
21mEstablishing Quality Assurance in Startup environment
36mHow programmers & testers can be productive
01h 09mScaling up with Embedded Testing