QualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
summary
A quality-engineering platform evolves from unit-heavy tests to a flattened pyramid that treats accessibility, performance and security as first-order concerns; the team builds an in-repo API framework in Java using Rest Assured and TestNG, UI automation in TypeScript with Nightwatch, cross-browser tests on BrowserStack, load tests with Gatling, Lighthouse CI for accessibility and Ghost Inspector for production-like UX. Quality runs as a product with embedded QE reps, monthly/quarterly metrics, smoke/nightly suites and a measurable shift from manual cross-platform checks to automated, CI-ready pipelines.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:50Last minute release blocker
- 1:31Roller coaster ride
- 1:44The main problem
- 2:14Pragmatic approach
- 4:26Process
- 7:03Technology
- 13:56The QualityOps Stack
- 14:31Left Shift
- 16:06Frameworks
- 18:26Accessibility
related talks
18mThe evolution of Quality Engineering
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
24mQuality Engineering: A Journey from traditional testing to ‘Shift-Left’ Mindset
15mQuality Engineering Journey from Shift Left to Shift Right and Beyond
46mQuality Engineering for DevOps Teams
12mConvergent Quality Engineering
41mQuality Transformation
43mLean QA: Automation, Monitoring, Experiments