This document provides an introduction to Behavior Driven Development (BDD). It discusses how BDD combines techniques from test-driven development, domain-driven design, and object-oriented analysis and design to facilitate collaboration between teams. It emphasizes that BDD is focused on conversations between stakeholders to understand requirements before automating tests. The document then demonstrates how to identify stakeholders and their goals, prioritize capabilities and risks, write user stories and acceptance criteria, and automate tests using Gherkin syntax with tools like Cucumber or SpecFlow.

1. @gil_zilberfeld@gil_zilberfeld
BDD Crash Course

2. @gil_zilberfeld
Hello!
I AM GIL ZILBERFELD
www.gilzilberfeld.com
www.everydayunittesting.com
@gil_zilberfeld

3. @gil_zilberfeld@gil_zilberfeld
Behavior Driven Development

4. @gil_zilberfeld
BDD
“Combines the general techniques and
principles of TDD with ideas from
DDD and OOAD to provide software
development and management teams with
shared tools and a shared process to
collaborate on software development..”

5. @gil_zilberfeld@gil_zilberfeld
It’s all about conversations!
Automation comes later

6. @gil_zilberfeld
Not the testing pyramid

7. @gil_zilberfeld
A story
◉ Who – Stakeholder
◉ Why – Goals
◉ What - Capabilities
◉ How - Implementation

8. @gil_zilberfeld

9. @gil_zilberfeld
Stakeholder
“An individual, group, or
organization, who may affect, be
affected by, or perceive itself to be
affected by a decision, activity, or
outcome of a project.”

10. @gil_zilberfeld
Stakeholders
◉ Users
◉ Customers
◉ Builders
◉ Regulators
◉ Bystanders

11. @gil_zilberfeld
Categorizing stakeholders
◉ Roles
◉ Jobs to be done (JTBD)
◉ What’s important for them?
◉ How does the product impact their lives?

12. @gil_zilberfeld@gil_zilberfeld
Who are the stakeholders of Airbnb?

13. @gil_zilberfeld
Testicorn – A killer app
The ghost of the
testing unicorn
that terrorizes the
city of Stockholm

14. @gil_zilberfeld
Exercise: Testicorn stakeholders
◉ List them
◉ Categorize them
◉ Rate them

15. @gil_zilberfeld

16. @gil_zilberfeld

17. @gil_zilberfeld
Goal
“A goal is a desired
result that a person or a
system envisions, plans
and commits to
achieve.”

18. @gil_zilberfeld@gil_zilberfeld
What are the goals of the stakeholders of Airbnb?

19. @gil_zilberfeld

20. @gil_zilberfeld
Capability
“An ability to perform or
achieve certain actions or
outcomes through a set of
controllable and measurable
faculties, features, functions,
processes, or services.”

21. @gil_zilberfeld
Exercise: Stakeholders goals and capabilities
◉ What is important to our stakeholders?
◉ What do they want to achieve?
◉ What options do we have to meet the goals?
◉ Prioritize them

22. @gil_zilberfeld

23. @gil_zilberfeld
Risk
“The potential of gaining or
losing something of value.”

24. @gil_zilberfeld@gil_zilberfeld
What are the risks of the stakeholders of Airbnb?

25. @gil_zilberfeld
Exercise: Stakeholder’s risks
◉ What can go wrong?
◉ What happens when things go wrong?
◉ Think about how risks relate to capabilities
◉ Prioritize them

26. @gil_zilberfeld@gil_zilberfeld
Why do we need to slice stories?

27. @gil_zilberfeld
Questions about stories
◉ Are the stories ready for work?
◉ Do they fit in a sprint?
◉ How complex are they?
◉ What will we learn?
◉ What options do we have for implementation?
◉ Do we need to do a POC?

28. @gil_zilberfeld
The template
As a …
I want a …
In order to …

29. @gil_zilberfeld
The template
As a killer unicorn
I want to get near a victim
In order to kill it

30. @gil_zilberfeld@gil_zilberfeld
What is the acceptance criteria?

31. @gil_zilberfeld@gil_zilberfeld
Give me an example!

32. @gil_zilberfeld
The template
As a killer unicorn
I need to be at least 12 steps
from a victim
In order to kill it

33. @gil_zilberfeld
Good user stories
Independent
Negotiable
Valuable
Estimable
Small
Testable
Bill Wake, 2003

34. @gil_zilberfeld
Good user stories
Independent
Negotiable
Valuable
Estimable
Small
Testable
Bill Wake, 2003

35. @gil_zilberfeld
Exercise
◉ Write stories for the capabilities and risks
◉ Remember who the stake holder is

36. @gil_zilberfeld@gil_zilberfeld
Gherkin
Finally some automation

37. @gil_zilberfeld
The keywords
Given
When
Then
And

38. @gil_zilberfeld
The scenario
Given the Testicorn is 12 steps
from the victim
When it tries to kill the victim
Then it succeeds

39. @gil_zilberfeld
The other scenario
Given the Testicorn is 50 steps
from the victim
When it tries to kill the victim
Then it fails

40. @gil_zilberfeld@gil_zilberfeld
Cucumber example

41. @gil_zilberfeld
Setting up Eclipse with Cucumber
◉ “Help”->”Add new software” from: Cucumber.io
◉ Create simple maven project
◉ Add the Cucumber dependencies
◉ Add to src/test/java a new .feature file
◉ Run and copy the generated errors to create
functions

42. @gil_zilberfeld
Setting up VS with SpecFlow
◉ Add the SpecFlow extenstion
◉ Create a unit test project
◉ Get SpecFlow.MsTest from NuGet
◉ Add New Item -> SpecFlow Feature file
◉ Write scenarios
◉ Right click -> Generate Step Definitions

43. @gil_zilberfeld
Summary
◉ It’s all about the shared understanding
◉ Shared language between users, product
people, developers and testers
◉ Gherkin tests help when there is code that is not
a shared language
◉ Part of the professional tool belt

44. @gil_zilberfeld
Thanks!
ANY QUESTIONS?
You can find me at:
@gil_zilberfeld
http://www.GilZilberfeld.com
http://www.EverydayUnitTesting.com