How Wayfair tests software. Shift left
summary
Catalog Engineering runs 24 teams, 200+ developers, 300+ web services and 100+ releases per day; Wayfair replaces embedded QEs with a central Quality & Test Automation Excellence team (now six QEs) and forces CI/CD pipelines with unit‑test coverage gates. They add static code analysis, vulnerability scanners, isolated local test environments, feature/supplier toggles, canary and A/B rollouts, dashboards and training. Result: branch coverage rises from ~37% to 64%, high‑severity escapes drop >50%, and teams own automation and rollback paths for fast, incremental delivery.
AI-written summary · about
chapters (18)
- 0:00Software quality challenges
- 1:12Agenda
- 1:53Rapid releases and defects
- 3:21Quality engineering challenges
- 5:32Hiring quality engineers
- 7:42Transforming analysts into engineers
- 9:08Shared quality ownership
- 10:51Five-step quality plan
- 14:22Quality improvements results
- 15:05Preventing defects via requirements
- 18:36Tools and processes for defects
- 20:45Teams owning quality
- 21:28Automated tests in CI/CD
- 22:29Feature toggles and canary deployments
- 24:58Monitoring and rollbacks
- 26:25Product health dashboards
- 26:46Key takeaways
- 27:08One-year results
related talks
46mWayfair Same-day Delivery: A Narrative in Painful Anecdotes about CI at Scale
01h 09mScaling up with Embedded Testing
18mThe evolution of Quality Engineering
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
31m#testedAF: Test All the Things (Not Just Your Units)
47mEvolution of Quality Engineering in Financial Services
31mApplying Shift Left Test Strategy for Higher Quality