EVERYTHING YOU MUST KNOW ABOUT AGILE TESTERS
summary
Concrete claims and practices appear here not platitudes testing shifts from finding bugs to preventing them and success is measurable like zero bugs as a goal the process uses executable specifications written in Given-When-Then style with Cucumber and SpecFlow story mapping and Three Amigos sessions create acceptance criteria with examples automation choices are explicit UI versus controller layer decisions and Selenium tradeoffs are discussed baseline data and reusable test building blocks get built and shown working in continuous verification
AI-written summary · about
chapters (13)
- 0:00Bevezetés
- 2:00Agile testing principles
- 7:02Bug Hunting -- Bug Prevention
- 8:06Requirements vs. Tests
- 11:58Develop test strategy
- 14:36Agile testers during preparation...
- 15:17Finding acceptance criteria
- 17:29Agile testers during planning...
- 17:58Formulate business readable tests
- 18:54Managing baseline (default) data
- 20:19Visualize systems
- 20:50Establish build status indicators
- 21:32Agile testers during Sprint...
related talks
58mAppendix A: What We´ve Learned Since Agile Testing
43mHow I fell in love with Agile testing and why you should, too!
33mAgile Software Testing
43mAgile Testing Practices for Better Software Quality
49mTest Strategy in a SCRUM Environment
36mContext-driven Agile Tester
01h 05mAdding value in an agile context
09m"A few things about Agile Testing"