Testing In Agile
summary
Argues that "Agile Testing" is a misnomer—testing remains testing—and recommends a concrete balance: keep exploratory testing as primary feedback while automating repeatable checks into SDET-style frameworks. Recommends using machine learning and predictive analytics to score and prioritize test cases so teams run far fewer but more valuable tests, and warns do not automate everything. Offers a practical strategy and checklist for shifting team roles, tooling, and test-case selection in Agile delivery.
AI-written summary · about
related talks
43mHow I fell in love with Agile testing and why you should, too!
33mAgile Software Testing
34mHelping Testers Add Value to Agile Projects
09m"A few things about Agile Testing"
58mAppendix A: What We´ve Learned Since Agile Testing
39mMyths & Challenges of Agile Testing
43mAgile Testing Practices for Better Software Quality
01h 05mAdding value in an agile context