Panel Discussion: Building Confidence in AI-Driven Testing Decisions
summary
Panelists lay out concrete practices: use RAG and model-versioning for data security, track provenance and audit trails for every AI-generated test, run eval at scale (many runs, not single outcomes) to catch non‑determinism, and deploy self-healing locators plus flakiness detection to reduce drift. Human‑in‑the‑loop gates remain mandatory: approve specs and plans before large code or test generation, log approvals, and measure sustainability so generated automation actually lowers technical debt.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 3:13Trust in AI testing decisions
- 8:32Automation vs human oversight
- 17:07AI adoption barriers
- 26:38Measuring AI testing success
- 39:37AI testing frameworks and metrics
- 49:02Future of AI-powered testing
- 1:03:11Closing
related talks
44mPanel Discussion | The AI Revolution in Testing: Opportunities and Challenges
46mPanel Discussion: Beyond vibe coding: Expanding AI’s role in delivery
43mAI for Testing – Panel Discussion
01h 05mPanel Discussion - The Future of Testing: Impact of AI in Quality Assurance and Beyond
32mQuality engineering in the AI age: From testing AI to leveraging GenAI
32mFast, Smart, and Fragile: Rethinking Testing Leadership in the Age of AI
46mThe Real Impact of AI in Software Testing
29mTesting and Assuring AI-Based Systems