Description:

So you’ve probably heard how agile people like to burn documentation. They may declare “WORKING SOFTWARE don’t need no stinkin’ documentation.”

But here’s a secret: They love testing. (Or at least they say they do ;). As a software tester you need to know about story testing (a.k.a acceptance test driven development). When done well, story testing empowers a team to increase collaboration between business, testing, design, and developers. Oh, and it creates valuable, living documentation. We all know communicating what ought be built is one of the hardest parts of making great software. Story tests give you: * An artifact for collaboration about what should be built * Feedback on how close to done your software is * Safety to know when a change breaks existing functionality

In this workshop, you’ll discover: * What story testing is * What frameworks exist for it * How to write story tests that provide maximum communicative power with minimum brittleness * How to break user stories and minimum marketable features into story tests