10 Things You Should Know About BDD, Cucumber And SpecFlow
This session looked at what Behaviour Driven Development is good for and what BDD tools you should be using. It looked at common BDD anti-patterns and myths, leading towards some advice that will help every organisation.
Both Behaviour Driven Development (BDD) and Specification By Example (SBE) are quite recent additions to the software development toolbox. Sometimes it feels like we’re using a hammer to drive in a screw, so in this session we’ll explore what they’re good for and when to use them. This webinar will also examine what problems both BDD and SBE are not useful for and when not to use them.
As you might expect, Seb is a huge fan of BDD using these tools when done properly, but he is also experienced the pain of organisations who have approached BDD from a test automation perspective. Once we’ve put that anti-pattern to bed, we’ll move on to looking at how to write maintainable executable specifications, organising large suites specifications in an accessible way and some of the technological solutions that can help.
Here you’ll have a brief look at some of the features that are shared (and differentiate) members of the Cucumber family.
By the end of this session you’ll know enough to decide whether your problems are more like a screw or a nail – and whether Cucumber/SpecFlow is the right hammer.
1) Understand what BDD really is.
2) Know how which BDD tools (and automation) fit into the BDD approach.
3) Dispel some of the more common BDD myths