The evolution of Quality Engineering
summary
Describes how Just Eat Takeaway builds a quality architecture that shifts QA and automation into a single quality engineer role, using SonarQube for code-quality gates, CI/CD pipelines to catch failures early, and Firebase reports aggregated by an AWS Lambda cron job that posts flaky UI test alerts to Slack. Explains choosing mocked vs live environments per test purpose, adds screenshot testing for UI layout checks, and cites the common stat that late-found bugs cost about six times more.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 0:47From QA to quality engineering
- 2:13Quality engineer role explained
- 3:39Efficient UI testing strategies
- 5:04Screenshot testing benefits
- 6:28Code quality with SonarQube
- 8:58CI/CD for reliable delivery
- 10:02TestOps for visibility
- 12:31Building quality architecture
- 14:39Future of quality engineering
related talks
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
49mIs your Quality on the Road to Nowhere?
47mEvolution of Quality Engineering in Financial Services
46mQuality Engineering for DevOps Teams
45mIs there a place for QA in modern agile autonomous fast-flow teams?
46mPanel Discussion: Quality Engineering - an Evolution of Software Quality as a Team Responsibility
35mWhy Software Engineers Should Make Quality a Priority