Quality Engineering Evolution: What Lies Ahead in
summary
Panelists report concrete shifts: teams run end-to-end runs twice daily in CI to catch regressions fast, adopt Playwright/Cypress/k6 and TestMu AI or LambdaTest for cross‑environment execution, and run prompt engineering micro-experiments to generate test cases and triage flakiness. They cite an industry stat — 70% increasing testing budgets — and recommend picking tools that fit current stacks, validating tool claims before buying, and keeping risk‑based exploratory testing as the guiding discipline.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:282024 experiences and achievements
- 10:40Evolving test pyramid
- 17:48Quality engineering roles
- 29:12Tech versus foundational testing
- 41:47Starting quality engineering
- 48:56Tool selection for testing
- 53:50Closing remarks
related talks
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
46mEvolution & Future of Software Testing
17mStaying Ahead: The Future of QA Leadership
47mHow Testing is Evolving in DevOps
12mConvergent Quality Engineering
47mEvolution of Quality Engineering in Financial Services
14mPrompt Engineering Impacts to Software Testers : Staying in Demand
38mEvolutionary Testing Strategy