Join Mary Thorn as she explores the nuances of Cucumber and shows you how to implement specification-by-example, behavior-driven development, and agile acceptance testing.
We’ve all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone.
But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests.
By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams. 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, be here!
YOU MAY ALSO LIKE:
Specification-by-Example: A Cucumber Implementation
Mary Thorn is a Director of QA at ChannelAdvisor in Morrisville, North Carolina. She has a broad testing background that spans automation, data warehouses, and web-based systems in a wide variety of technologies and testing techniques.