Improved Regression Testing in Agile
summary
Claims a concrete method: divide regression into six-group heuristic (recent, core, risky, configuration‑sensitive, repaired, chronic) and run a short smoke test daily, not full retest cycles that sometimes stretch months or a year. Automate backend and automate web services and performance checks, keep UI automation minimal, run overnight to get results in hours. Use ticketing dashboards not Excel, trace changes via git and REST calls, and retire repeat‑failing pesticide tests that stop finding new bugs.
AI-written summary · about
chapters (8)
- 0:00Improved regression testing intro
- 3:18What is regression testing
- 10:02Common mistakes in regression
- 19:51Six groups for regression
- 23:42Testing each group separately
- 32:12Optimizing regression in Agile
- 34:20Beyond traditional regression
- 36:24Q&A
related talks
45mOptimization of Regression Tests
33mRegression Is My Profession!
43mRegression Obsession
39mThe Good Testing, The Bad Testing and The Ugly Testing
07mInterview on Regression Testing and Continuous Delivery
46mEffective regression testing using an adaptive approach
46mEffective regression testing using an adaptive approach
24mImproving Development Quality and Speed with Agile Testing
