Abstract

Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Even well-groomed, refined stories, framed with typical, alternate, and error scenarios and gracefully described in well-formed Gherkin, continue to encounter all sorts of bugs.

Software engineering consultant Rob Sabourin sees rework in over 20 per cent of deployed stories, but he can show you how agile teams can drive rework down dramatically, often achieving near-zero rework after a story is done. Rob teaches teams to identify and implement relevant testing activities above and beyond those derived from well-formed requirements. He seeks out testing ideas relevant to what is really being changed in the technological solution, finds ideas based on what the user actually does in the workplace, and discovers rich test ideas based on the target environments.

You will learn many excellent strategies to identify, prioritize, and implement reality-driven testing so you can ferret out important bugs that really matter, eliminating the need for downstream rework.

Top Takeaways:

• There is a lot more to agile testing than automating story and unit regression tests.
• Reality drives awesome test ideas based on what has really changed, what users really do and what environment is really being used.