Getting Started with Acceptance Test-Driven / Behavior-Driven Development
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD) and Acceptance Test Driven Development (ATDD) practices that help facilitate better communication. Mary explores the nuances of BDD and ATDD and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, tools like Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.