Better Gherkin: Common pitfalls and how to overcome them

Many organizations are adopting Behavior Driven Development (or BDD) to build a shared understanding across business and technical domains. To that end, Gherkin has emerged as a popular BDD tool to document the intended behavior of a system in a way that can be clearly understood by everyone with the added benefit that these executable specifications can be transformed into automated tests. Sounds easy, right? Well, here's the not so great news. Writing is an art and so is writing good Gherkin scenarios. In our experience, far too many teams who have adopted BDD practices, write Gherkin scenarios that are difficult to understand, brittle and prone to narrow use. In this talk we will discuss some of the common anti-patterns we’ve observed and provide tips and tricks for improving your Gherkin scenarios. With these tips, you’ll be writing Gherkin feature files like a pro! Remember the Golden Gherkin Rule: Write Gherkin so that people who don’t know the feature will understand it! https://lithespeed.com/dc-leanagile-f... Sign up for our newsletter: https://lithespeed.com/newsletter/ Learn about our training offerings: https://lithespeed.com/agile-and-scru... Check out our Agile Leadership Academy: https://agileleadershipacademy.com/