Reality-Driven Testing in Agile Projects (continued)
Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Well-groomed, refined stories framed with typical, alternate, and error scenarios, gracefully described in well-formed Gherkin, continue to encounter all sorts of bugs. In fact, software engineering consultant Rob Sabourin sees rework in over 20% of deployed stories. Rob will show how agile teams can drive rework down dramatically, often achieving near-zero rework after a story is done, by prioritizing reality-driven testing. He’ll teach you to identify and implement relevant testing activities above and beyond those derived from well-formed requirements. You’ll learn to seek out testing ideas based on what is being changed in the technological solution, to think about what the user actually does in the workplace, and to create rich test ideas based on real target environments. You’ll get many excellent strategies to ferret out important bugs that truly matter, to eliminate the need for downstream rework, and to identify, prioritize, and implement tests based on reality.