In this webinar, Mike Scott, Principle consultant at MagenTys and Kevin Dunne, VP of Strategy and Business Development at QASymphony dove into why Behavior Driven Development (BDD) is gaining momentum, how BDD can be implemented into your organization and how to overcome several of the challenge you are likely to run in to.
“BDD is not a test of technique or process. It is about collaboration and communication.” – Mike Scott
Why do we do BDD?
BDD is one of those things that gets the conversation going. The more you have to read, the more you will miss. It’s about finding a concise way to convey what it is that people want and what it is that is important to them.
Here’s a map of the BDD Cycle :
“BDD is collaborative and story-centric”
You must discuss the problem and align on interests!
Here are 4 key takeaways:
Prepare- prepare story and overall context
Build- build it, explore it
Review- monitor, evaluate
It is important to get acceptance criteria, detail out key examples, and make sure we understand the key educators.
Specification by Example :
Examples can become tests
Examples can be used to elaborate your requirements
Tests can verify that the requirements have been met
And the Result? The examples of the scenarios can become a single source of truth and reduce ambiguity.
Ground common understanding
Reduce ambiguity and handoffs
Single source of truth
Target for development
Here are the 3 C’s of this cycle!
Example mapping uses cards to structure the conversation and provides concrete examples for confirmation.
Here’s how it works:
6 Steps to example mapping:
Write the story on a yellow card
Write each rule/acceptance criteria on a blue card