Example Mapping
Fleeting- External reference: https://cucumber.io/blog/bdd/example-mapping-introduction/
Introducing Example Mapping
- see,
We start by writing the story under discussion on a yellow card and placing it at the top of the table.
Next we write each of the acceptance criteria, or rules that we already know, on a blue card and placing those across the table beneath the yellow story card.
For each rule, we may need one or more examples to illustrate it. We write those on a green card and place them under the relevant rule.
As we discuss these examples, we may uncover questions that nobody in the room can answer. We capture those on a red card and move on with the conversation.
We keep going until the group is satisfied that the scope of the story is clear, or we run out of time.
And that’s it
— https://cucumber.io/blog/bdd/example-mapping-introduction/
quickly build up a visual representation on the table in front of us reflecting back our current understanding of the story
— https://cucumber.io/blog/bdd/example-mapping-introduction/
instead of going for full-blown formal Gherkin scenarios, just try to capture a list of rough examples, using the friends episode naming convention
— https://cucumber.io/blog/bdd/example-mapping-introduction/
For example:
The one where the customer forgot his receipt The one where the product is damaged The one where the product was bought 15 days ago
— https://cucumber.io/blog/bdd/example-mapping-introduction/
turned an unknown unknown into a known unknown
— https://cucumber.io/blog/bdd/example-mapping-introduction/
three amigos: a developer, a tester and a product person
— https://cucumber.io/blog/bdd/example-mapping-introduction/
help to have someone in the formal role of facilitator,
— https://cucumber.io/blog/bdd/example-mapping-introduction/
takes discipline to capture them on the table so you can see what you’re talking about
— https://cucumber.io/blog/bdd/example-mapping-introduction/
my preference is for the product person to spend their time and energy in the example mapping session, and leave the actual writing of Gherkin to their other two amigos. Once they’ve drafted a Gherkin specification, the product person can give them feedba
— https://cucumber.io/blog/bdd/example-mapping-introduction/
every other day is often a good rhythm. Just pick one story and give it 25 minutes of attention, then go back to work. Trying to do more in a big batch will just drain your energy.
— https://cucumber.io/blog/bdd/example-mapping-introduction/
key is to keep it quick and easy to work with, so you can focus on the conversation.
— https://cucumber.io/blog/bdd/example-mapping-introduction/