Myths & Challenges of Agile Testing
summary
Claims include 90% of all data created in the last two years and over 80% of companies moving to agile, with Standish-style figures that a third of projects cancel. Agile testing shifts from end-stage bug detection to early bug prevention through acceptance criteria, reviews and developer collaboration. Automation is framed as a development activity done for confidence not primary defect discovery, regression suites are expensive to maintain, and performance testing is often skipped until production failures force firefighting.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:16Agile Testing
- 13:22Baby Duck Syndrome
- 19:16Negative Testing
- 23:10Devops
- 23:45Continuous Integration
- 25:42Distribute the Testing Responsibility
- 33:05Dynamic and Static Testing
related talks
43mHow I fell in love with Agile testing and why you should, too!
36mYou Can't Be Agile If Your Testing Practices Suck
08mTesting In Agile
24mImproving Development Quality and Speed with Agile Testing
09m"A few things about Agile Testing"
58mAppendix A: What We´ve Learned Since Agile Testing
33mAgile Software Testing
45mSpeeding Up Delivery and Raising Quality with Agile Testing