"A few things about Agile Testing"
summary
Defines Agile Testing via Lisa Crispin and Janet Gregory as continuous, collaborative testing that builds quality in and urges Agile ≠ Scrum as a core correction. Lists concrete pitfalls: delayed requirements, separate testing sprints, missing test strategy and no risk management. Recommends practices: analyze risk to identify tests early (example: retail site unusable with scripts off), translate user stories into tests (reorder feature: out‑of‑stock, price change, system error) and apply Dan Ashby’s continuous testing model with exploratory tests before check‑in.
AI-written summary · about
related talks
43mHow I fell in love with Agile testing and why you should, too!
08mTesting In Agile
43mAgile Testing Practices for Better Software Quality
58mAppendix A: What We´ve Learned Since Agile Testing
33mAgile Software Testing
39mMyths & Challenges of Agile Testing
34mHelping Testers Add Value to Agile Projects
44mFive Key Challenges for Agile Testers tomorrow