Beyond Bugs: How AI turns QA into Full-Circle Engineers
summary
Claims that AI makes QA full engineers get grounded in specifics: Zencoder’s ZenFlow runs an agent fleet, a PR test-coverage bot suggests P1/P2 scenarios and ranks missing tests, integrations pull from Sentry/logs for root‑cause analysis, and AI produces video reproductions that click, verify and sometimes patch UI bugs. Costs matter (example: ~$2.50 API bill for one feature on GPT‑4), failures happen (Opus 4.7 can skip steps), and a cited QA firing led to a $6M outage—so expect concrete gains, limits, and measurable tradeoffs.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:04AI adoption trends
- 2:28Speaker background
- 4:54AI evolution and impact
- 6:16ZenFlow and QA challenges
- 8:01AI writing tests
- 9:47Automated bug feedback
- 10:52Root cause analysis
- 11:35AI fixing bugs
- 15:25Can AI replace QAs
- 16:49Cost and prioritization
- 17:51Rising QA demand
- 20:17Future of QA with AI
- 20:58Closing remarks
related talks
48mBeyond Bugs: How AI Turns QA into Full-Cycle Engineers
40mFrom Bugs to Brilliance: Leveraging AI in Modern Software Testing
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
42mIt's Inevitable, Mr. Anderson: Machines, Humans, and the Future of Testing
42mThe Power of Human and AI Collaboration in Software Testing
29mQA vs AI: Friends or Foes?
47mPanel Discussion: Who Tests the Machines? QE Leaders on Quality in the Age of AI-Written Code
37mAgentic AI and the Next Decade of Quality Engineering