SlideShare a Scribd company logo

BDD in Action - building software that matters

John Ferguson Smart Limited, profile picture
John Ferguson Smart Limited

The document outlines the principles of Behavior-Driven Development (BDD) as a collaborative process that improves the understanding of software requirements among business owners, analysts, developers, and testers. It emphasizes the importance of conversations and structured examples to clarify requirements and facilitate automation of acceptance criteria, leading to more effective software development. The use of living documentation and executable specifications is highlighted as a means to ensure quality and align software features with business goals.

TechnologyBusiness
1 of 159
Downloaded 811 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
BDD
in action Building software that matters
John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
So what is this BDD thing?
Using examples So what is this BDD thing?
Using examples a shared understanding So what is this BDD thing?
Using examples a shared understanding software that matters So what is this BDD thing?
BDD So what is this BDD thing?
BDD Collaboration So what is this BDD thing?
BDD Hunting out value Collaboration So what is this BDD thing?
BDD Hunting out value Collaboration Building the right software So what is this BDD thing?
BDD Hunting out value Automated Acceptance Criteria Collaboration Building the right software So what is this BDD thing?
BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the right software So what is this BDD thing?
BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the software right Building the right software So what is this BDD thing?
BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the software right Building the right software Living Documentation So what is this BDD thing?
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" •Specifica8ons  are  elaborated  collabora8vely   •Specifica8ons  use  a  common  language   •Executable  specifica8ons  provide  fast  feedback BDD in a nutshell
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Solves the wrong problem well
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Solves the wrong problem well Solves the right problem poorly
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Solves the wrong problem well Solves the right problem poorly
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Slow to change Solves the wrong problem well Solves the right problem poorly
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Hard to maintain Slow to change Solves the wrong problem well Solves the right problem poorly
“software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Hard to maintain Slow to change Does what the business needs Reliable Easy to maintain Solves the wrong problem well Solves the right problem poorly
You don’t know what you don’t know Understanding of what needs to be delivered Time
You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done
You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done
You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done •Our  ignorance  decreases  over  8me   •It  does  not  decrease  at  a  linear  rate   •It  does  not  always  decrease  in  a  predictable  way
Business Goal Business Goal Business Goal “software that matters” We  start  with  a  business  goal
Business Goal Business Goal Business Goal “software that matters” We  start  with  a  business  goal “Increase  *cket  sales  by  5%  over  the  next  year   by  encouraging  travelers  to  fly  with  Flying  High   rather  than  with  a  rival  company.”
Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures
Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights
Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights Earn  Frequent  Flyer  points  from  purchases
Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights Earn  Frequent  Flyer  points  from  purchases View  Frequent  Flyer  account  balance  online
Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples
Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status”
Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member”
“Using examples”
“Using examples” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
“Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
“Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
“Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member” “If  I  ask  for  the  details  about  the  flight  FH-­‐102,  I  should  see  that   it  is  a  Sydney  to  Hong  Kong  flight  that  leaves  at  11:55pm  ” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
“Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
“Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
“Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
“Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
“Using examples” The  automated  acceptance  criteria   guide  the  development  process
“Using examples” The  automated  acceptance  criteria   guide  the  development  process
“Using examples” The  automated  acceptance  criteria   guide  the  development  process
“a shared understanding”
“Having  the  conversa/on     is  more  important  than     recording  the  conversa/on   is  more  important  than     automa/ng  the  conversa/on”   -­‐  Liz  Keogh “a shared understanding”
BA Developer Tester Many teams build features like this… “a shared understanding”
Story BA Developer Tester Many teams build features like this… “a shared understanding”
Story Working   code BA Developer Tester Many teams build features like this… “a shared understanding”
Story Working   code boring   manual   tes5ng BA Developer Tester Many teams build features like this… “a shared understanding”
Story bug  reports Working   code boring   manual   tes5ng BA Developer Tester Many teams build features like this… “a shared understanding”
Story bug  reports Working   code boring   manual   tes5ng WASTE BA Developer Tester Many teams build features like this… “a shared understanding”
…but a little cooperation goes a long way… Story “a shared understanding”
…but a little cooperation goes a long way… Story “a shared understanding”
…but a little cooperation goes a long way… Story “a shared understanding”
…but a little cooperation goes a long way… Story “a shared understanding”
…but a little cooperation goes a long way… Story Examples “a shared understanding”
…but a little cooperation goes a long way… Story Examples Automated   acceptance   criteria “a shared understanding”
…but a little cooperation goes a long way… Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
…but a little cooperation goes a long way… Working  code     and     Working  Automated   Acceptance  Tests Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
…but a little cooperation goes a long way… Working  code     and     Working  Automated   Acceptance  Tests Exploratory  tes5ng,   usability  tes5ng... Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
We call this “The Three Amigos” BA  and/or  product  owner Tester Developer Automatable   Acceptance   Criteria Shared   understanding “a shared understanding”
We call this “The Three Amigos” “a shared understanding”
We call this “The Three Amigos” “a shared understanding”
We call this “The Three Amigos” “a shared understanding”
We call this “The Three Amigos” “a shared understanding”
We call this “The Three Amigos” “a shared understanding”
“Automation without collaboration is empty”
Living Documentation
Living Documentation
Living Documentation Illustrates  delivered  features
Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features
Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features Progress  repor5ng
Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features Func5onal  and  technical  documenta5on Progress  repor5ng
Automated test results tell us…
Automated test results tell us… How  many   tests  passed
Automated test results tell us… How  many  failed How  many   tests  passed
Automated test results tell us… How  many  failed How  many   tests  passed How  many  weren’t  run
Automated test results tell us…
Automated test results tell us… What  tests  exist  for   a  given  feature
Automated test results tell us… What  tests  exist  for   a  given  feature How  stable  the  feature  is
Automated test results tell us…
Automated test results tell us… How  a  feature  was   tested
Automated test results tell us…
Automated test results tell us… What  a  feature  looks  like
Automated test results tell us…
Automated test results tell us… What  a  feature  looks  like
Automated test results tell us… What  a  feature  looks  like
Test results do not tell us what was not tested
Feature Coverage
Feature Coverage What  stories  are  defined   for  this  feature?
Feature Coverage What  stories  are  defined   for  this  feature? How  many  stories  have  automated   acceptance  criteria?
Feature Coverage What  stories  are  defined   for  this  feature? How  many  stories  have  automated   acceptance  criteria? What  acceptance  criteria  have   been  automated?
“Living Documentation completes the circle”
Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications spock RSpec “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications spock RSpec “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
“building the software right”
Acceptance  criteria  tell  us  what  we  need  to  build… “building the software right”
“building the software right”
What  would  we  like  the  API  to  look  like? “building the software right”
What  would  we  like  the  API  to  look  like? “building the software right”
What  would  we  like  the  API  to  look  like? “building the software right”
“building the software right”
Then  write  low-­‐level  specifica8ons  for  the  code “building the software right”
Then  write  low-­‐level  specifica8ons  for  the  code “building the software right”
“building the software right”
“building the software right” These  low  level  specifica8ons  become  technical   documenta8on  for  your  APIs
“Every class is an API for someone”
BDD Gotchas 1 2 3 4
BDD Gotchas 1 2 3 4 An8-­‐paQern  1   The  business  analyst  writes  the  scenarios  and  then  gives   them  to  the  other  team  members.
1 2 3 4 BDD Gotchas
1 2 3 4 BDD Gotchas An8-­‐paQern  2   The  tester  writes  the  scenarios  at  the  end   to  implement  an  automated  test  suite.
1 2 3 4 5 BDD Gotchas
1 2 3 4 5 BDD Gotchas An8-­‐paQern  3   The  “Three  Amigos”  sessions  don’t  result  in  usable  scenarios,  so  the   developer  invents  them  a?erwards.
1 2 3 4 5 BDD Gotchas An8-­‐paQern  3   The  “Three  Amigos”  sessions  don’t  result  in  usable  scenarios,  so  the   developer  invents  them  a?erwards.
1 2 3 4 5 BDD Gotchas
1 2 3 4 5 BDD Gotchas An8-­‐paQern  4   The  scenarios  are  too  UI-­‐centric  or  detail-­‐focused,  and  neglect  to  express   the  core  business  value.
42 Benefits of BDD •Focus  effort   •Reduce  waste  and  misaligned  requirements
43 Benefits of BDD Deliver  more  valuable  soYware
44 Benefits of BDD Make  changes  safely
45 Benefits of BDD Faster  and  more  reliable  releases
46 Benefits of BDD Reduced  maintenance  costs
BDD  requires  high  business  engagement  and  collabora8on   Adoption challenges
BDD  works  best  in  an  Agile  or  Itera8ve  context   Adoption challenges
BDD  does  not  work  well  in  a  silo   Adoption challenges
Adoption challenges Skill  and  prac,ce  required:   •Wri,ng  good  scenarios  takes  prac,ce   •Poorly  wri:en  tests  can  lead  to  higher  test-­‐maintenance  costs   •Need  to  treat  test  automa,on  code  like  produc,on  code  
In conclusion… It’s  behaviour  all  the  way  down
Want to learn more?
Want to learn more?
Want to learn more? http://thucydides.info/
Want to learn more? http://thucydides.info/ https://code.google.com/p/spock/
Thank You John Ferguson Smart john.smart@wakaleo.com wakaleo http://www.wakaleo.com

More Related Content

PDF
BDD in Action – principles, practices and real-world application
John Ferguson Smart Limited
 
PPTX
Gherkin /BDD intro
Ryan Thomas Hewitt★CSM★CSPO★ITIL
 
PPTX
Introduction to Bdd and cucumber
Nibu Baby
 
PPTX
Sexy Using Cucumber - BDD in your project
b4usolution .
 
PPTX
BDD testing with cucumber
Daniel Kummer
 
PDF
BDD & Cucumber
Vladimir Arutin
 
PPTX
Cucumber BDD
Pravin Dsilva
 
ODP
Introduction to BDD
Knoldus Inc.
 
BDD in Action – principles, practices and real-world application
John Ferguson Smart Limited
 
Gherkin /BDD intro
Ryan Thomas Hewitt★CSM★CSPO★ITIL
 
Introduction to Bdd and cucumber
Nibu Baby
 
Sexy Using Cucumber - BDD in your project
b4usolution .
 
BDD testing with cucumber
Daniel Kummer
 
BDD & Cucumber
Vladimir Arutin
 
Cucumber BDD
Pravin Dsilva
 
Introduction to BDD
Knoldus Inc.
 

What's hot (20)

PPTX
Test Automation Framework with BDD and Cucumber
Rhoynar Software Consulting
 
PPTX
React Native
Software Infrastructure
 
PDF
Successfully Implementing BDD in an Agile World
SmartBear
 
PDF
An introduction to Behavior-Driven Development (BDD)
Suman Guha
 
PPTX
BDD WITH CUCUMBER AND JAVA
Srinivas Katakam
 
PPTX
BDD and Behave
Adam Englander
 
PDF
Behavior Driven Development with Cucumber
Brandon Keepers
 
PDF
Introduction to React Native
Sambhu Lakshmanan
 
PPTX
How native is React Native? | React Native vs Native App Development
Devathon
 
PPTX
Introduction to Behaviour Driven Development
Christophe Achouiantz
 
PDF
Introduction to BDD with Cucumber for Java
Seb Rose
 
PPTX
Bdd – with cucumber and gherkin
Arati Joshi
 
PPT
Cucumber presentation
Akhila B
 
PPTX
BDD presentation
temebele
 
PDF
Devops Porto - CI/CD at Gitlab
Filipa Lacerda
 
PDF
Intro to react native
ModusJesus
 
PDF
Cucumber ppt
Qwinix Technologies
 
PDF
Cypress e2e automation testing - day1 intor by: Hassan Hameed
Hassan Muhammad
 
PPTX
Cucumber presenation
Oussama BEN WAFI
 
PPTX
What Is Cucumber?
QATestLab
 
Test Automation Framework with BDD and Cucumber
Rhoynar Software Consulting
 
React Native
Software Infrastructure
 
Successfully Implementing BDD in an Agile World
SmartBear
 
An introduction to Behavior-Driven Development (BDD)
Suman Guha
 
BDD WITH CUCUMBER AND JAVA
Srinivas Katakam
 
BDD and Behave
Adam Englander
 
Behavior Driven Development with Cucumber
Brandon Keepers
 
Introduction to React Native
Sambhu Lakshmanan
 
How native is React Native? | React Native vs Native App Development
Devathon
 
Introduction to Behaviour Driven Development
Christophe Achouiantz
 
Introduction to BDD with Cucumber for Java
Seb Rose
 
Bdd – with cucumber and gherkin
Arati Joshi
 
Cucumber presentation
Akhila B
 
BDD presentation
temebele
 
Devops Porto - CI/CD at Gitlab
Filipa Lacerda
 
Intro to react native
ModusJesus
 
Cucumber ppt
Qwinix Technologies
 
Cypress e2e automation testing - day1 intor by: Hassan Hameed
Hassan Muhammad
 
Cucumber presenation
Oussama BEN WAFI
 
What Is Cucumber?
QATestLab
 
Ad

Similar to BDD in Action - building software that matters (20)

PDF
BDD in Action: Building Software Right and Building the Right Software
John Ferguson Smart Limited
 
PDF
BDD Anti-patterns
John Ferguson Smart Limited
 
PDF
It's Testing, Jim, but not as we know it - BDD for Testers
John Ferguson Smart Limited
 
PDF
BDD in Action - Automated Web Testing with WebDriver and Serenity
John Ferguson Smart Limited
 
PDF
Its testing-jim-but-not-as-we-know-it-devoxx
John Ferguson Smart Limited
 
PPTX
Behavior Driven Development
Adam Englander
 
PPTX
Cucumber is a Behavior Driven Development tool used to develop test cases for...
sahakrishnan
 
PPTX
Topic tdd-and-bdd b4usolution
Hoa Le
 
PPTX
Building In Quality: The Beauty Of Behavior Driven Development (BDD)
Synerzip
 
PDF
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
QA or the Highway
 
PDF
BDD in Action - Devoxx 2014
John Ferguson Smart Limited
 
PPTX
Gateway to Agile: XP and BDD
Gervais Johnson, Advisor
 
PPTX
Behavior Driven Development with AngularJS & Jasmine
Remus Langu
 
PDF
The BDD Process (Behavior-driven development)
GleecusTechlabs1
 
PDF
Being Test-Driven: It's not really about testing
Raj Indugula
 
PPTX
BDD 001 behavoir draven delopment ts.pptx
mahmoudabdelaty96
 
PDF
Testing stage. being ahead business with cucumber
Alex Mikitenko
 
PDF
BA and Beyond 20 - Elke Steegmans and David Vandenbroeck - Behaviour-driven d...
BA and Beyond
 
PPTX
Wednesday Webinar on "Strengthening your Agility with BDD - A demo using Cucu...
Agile Testing Alliance
 
PDF
Whole team approach to agile testing bdd can help better pune 15th meetup
Agile Testing Alliance
 
BDD in Action: Building Software Right and Building the Right Software
John Ferguson Smart Limited
 
BDD Anti-patterns
John Ferguson Smart Limited
 
It's Testing, Jim, but not as we know it - BDD for Testers
John Ferguson Smart Limited
 
BDD in Action - Automated Web Testing with WebDriver and Serenity
John Ferguson Smart Limited
 
Its testing-jim-but-not-as-we-know-it-devoxx
John Ferguson Smart Limited
 
Behavior Driven Development
Adam Englander
 
Cucumber is a Behavior Driven Development tool used to develop test cases for...
sahakrishnan
 
Topic tdd-and-bdd b4usolution
Hoa Le
 
Building In Quality: The Beauty Of Behavior Driven Development (BDD)
Synerzip
 
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
QA or the Highway
 
BDD in Action - Devoxx 2014
John Ferguson Smart Limited
 
Gateway to Agile: XP and BDD
Gervais Johnson, Advisor
 
Behavior Driven Development with AngularJS & Jasmine
Remus Langu
 
The BDD Process (Behavior-driven development)
GleecusTechlabs1
 
Being Test-Driven: It's not really about testing
Raj Indugula
 
BDD 001 behavoir draven delopment ts.pptx
mahmoudabdelaty96
 
Testing stage. being ahead business with cucumber
Alex Mikitenko
 
BA and Beyond 20 - Elke Steegmans and David Vandenbroeck - Behaviour-driven d...
BA and Beyond
 
Wednesday Webinar on "Strengthening your Agility with BDD - A demo using Cucu...
Agile Testing Alliance
 
Whole team approach to agile testing bdd can help better pune 15th meetup
Agile Testing Alliance
 
Ad

More from John Ferguson Smart Limited (20)

PPTX
My Reading Specs - Refactoring Patterns for Gherkin Scenarios
John Ferguson Smart Limited
 
PDF
Artisti e Condotierri - How can your team become artists of the 21st century ...
John Ferguson Smart Limited
 
PDF
Engage! Bringing teams together to deliver software that makes a difference
John Ferguson Smart Limited
 
PDF
BE A POD OF DOLPHINS, NOT A DANCING ELEPHANT
John Ferguson Smart Limited
 
PDF
Sustainable Test Automation with Serenity BDD and Screenplay
John Ferguson Smart Limited
 
PDF
Feature Mapping Workshop
John Ferguson Smart Limited
 
PDF
Engage! Bringing teams together to deliver software that makes a difference
John Ferguson Smart Limited
 
PDF
Beyond Given/When/Then - why diving into Cucumber is the wrong approach to ad...
John Ferguson Smart Limited
 
PDF
Beyond Given/When/Then - why diving into Cucumber is the wrong approach to ad...
John Ferguson Smart Limited
 
PDF
Shift left-devoxx-pl
John Ferguson Smart Limited
 
PDF
Screenplay - Next generation automated acceptance testing
John Ferguson Smart Limited
 
PDF
Cucumber and Spock Primer
John Ferguson Smart Limited
 
PDF
All the world's a stage – the next step in automated testing practices
John Ferguson Smart Limited
 
PDF
CukeUp 2016 Agile Product Planning Workshop
John Ferguson Smart Limited
 
PDF
BDD Anti-patterns
John Ferguson Smart Limited
 
PDF
Serenity and the Journey Pattern
John Ferguson Smart Limited
 
PDF
BDD - Collaborate like you mean it!
John Ferguson Smart Limited
 
PDF
BDD-Driven Microservices
John Ferguson Smart Limited
 
PDF
BDD: The unit test of the product owner
John Ferguson Smart Limited
 
PDF
TDD and BDD in Java 8 - what's in it for me?
John Ferguson Smart Limited
 
My Reading Specs - Refactoring Patterns for Gherkin Scenarios
John Ferguson Smart Limited
 
Artisti e Condotierri - How can your team become artists of the 21st century ...
John Ferguson Smart Limited
 
Engage! Bringing teams together to deliver software that makes a difference
John Ferguson Smart Limited
 
BE A POD OF DOLPHINS, NOT A DANCING ELEPHANT
John Ferguson Smart Limited
 
Sustainable Test Automation with Serenity BDD and Screenplay
John Ferguson Smart Limited
 
Feature Mapping Workshop
John Ferguson Smart Limited
 
Engage! Bringing teams together to deliver software that makes a difference
John Ferguson Smart Limited
 
Beyond Given/When/Then - why diving into Cucumber is the wrong approach to ad...
John Ferguson Smart Limited
 
Beyond Given/When/Then - why diving into Cucumber is the wrong approach to ad...
John Ferguson Smart Limited
 
Shift left-devoxx-pl
John Ferguson Smart Limited
 
Screenplay - Next generation automated acceptance testing
John Ferguson Smart Limited
 
Cucumber and Spock Primer
John Ferguson Smart Limited
 
All the world's a stage – the next step in automated testing practices
John Ferguson Smart Limited
 
CukeUp 2016 Agile Product Planning Workshop
John Ferguson Smart Limited
 
BDD Anti-patterns
John Ferguson Smart Limited
 
Serenity and the Journey Pattern
John Ferguson Smart Limited
 
BDD - Collaborate like you mean it!
John Ferguson Smart Limited
 
BDD-Driven Microservices
John Ferguson Smart Limited
 
BDD: The unit test of the product owner
John Ferguson Smart Limited
 
TDD and BDD in Java 8 - what's in it for me?
John Ferguson Smart Limited
 

Recently uploaded (20)

PDF
Dropbox Q2 2025 Financial Results & Investor Presentation
Dropbox
 
PDF
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
flufftailshop
 
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
SandeepSingh286037
 
PPT
Teaching material agriculture food technology
LiaRayya
 
PDF
Review of recent advances in non-invasive hemoglobin estimation
IAESIJAI
 
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 
PPTX
Cloud computing and distributed systems.
kkkkkhan
 
PDF
Spectral efficient network and resource selection model in 5G networks
IAESIJAI
 
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 
PDF
Chapter 3 Spatial Domain Image Processing.pdf
Getnet Tigabie Askale -(GM)
 
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
PDF
Encapsulation theory and applications.pdf
gurumoop
 
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
PPTX
MYSQL Presentation for SQL database connectivity
Swati270511
 
PDF
NewMind AI Weekly Chronicles - August'25 Week I
NewMind AI
 
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
Akar16
 
PDF
cuic standard and advanced reporting.pdf
SimoneTitaniumTomase
 
PDF
Electronic commerce courselecture one. Pdf
OmerMohamed64
 
Dropbox Q2 2025 Financial Results & Investor Presentation
Dropbox
 
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
Mobile App Security Testing_ A Comprehensive Guide.pdf
flufftailshop
 
Building Integrated photovoltaic BIPV_UPV.pdf
SandeepSingh286037
 
Teaching material agriculture food technology
LiaRayya
 
Review of recent advances in non-invasive hemoglobin estimation
IAESIJAI
 
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 
Cloud computing and distributed systems.
kkkkkhan
 
Spectral efficient network and resource selection model in 5G networks
IAESIJAI
 
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 
Chapter 3 Spatial Domain Image Processing.pdf
Getnet Tigabie Askale -(GM)
 
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
Encapsulation theory and applications.pdf
gurumoop
 
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
MYSQL Presentation for SQL database connectivity
Swati270511
 
NewMind AI Weekly Chronicles - August'25 Week I
NewMind AI
 
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
Akar16
 
cuic standard and advanced reporting.pdf
SimoneTitaniumTomase
 
Electronic commerce courselecture one. Pdf
OmerMohamed64
 

BDD in Action - building software that matters

  • 2. John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
  • 3. John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
  • 4. John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
  • 5. John Ferguson Smart Consultant   Trainer   Mentor   Author   Speaker   Coder
  • 6. So what is this BDD thing?
  • 7. Using examples So what is this BDD thing?
  • 8. Using examples a shared understanding So what is this BDD thing?
  • 9. Using examples a shared understanding software that matters So what is this BDD thing?
  • 10. BDD So what is this BDD thing?
  • 11. BDD Collaboration So what is this BDD thing?
  • 12. BDD Hunting out value Collaboration So what is this BDD thing?
  • 13. BDD Hunting out value Collaboration Building the right software So what is this BDD thing?
  • 14. BDD Hunting out value Automated Acceptance Criteria Collaboration Building the right software So what is this BDD thing?
  • 15. BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the right software So what is this BDD thing?
  • 16. BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the software right Building the right software So what is this BDD thing?
  • 17. BDD Hunting out value Automated Acceptance Criteria API and code design Collaboration Building the software right Building the right software Living Documentation So what is this BDD thing?
  • 18. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 19. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 20. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 21. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 22. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 23. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 24. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 25. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 26. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 27. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 28. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process
  • 29. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 30. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 31. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 32. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 33. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 34. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" BDD in a nutshell A BDD development process
  • 35. The business owner and the business analyst have a conversation about what he needs. 1 2 3 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The business analyst, the developer and the tester elaborate the requirements together. The scenarios guide the developer and act as automated tests They define requirements as structured, English- language format "scenarios" •Specifica8ons  are  elaborated  collabora8vely   •Specifica8ons  use  a  common  language   •Executable  specifica8ons  provide  fast  feedback BDD in a nutshell
  • 36. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship
  • 37. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Solves the wrong problem well
  • 38. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Solves the wrong problem well Solves the right problem poorly
  • 39. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Solves the wrong problem well Solves the right problem poorly
  • 40. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Slow to change Solves the wrong problem well Solves the right problem poorly
  • 41. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Hard to maintain Slow to change Solves the wrong problem well Solves the right problem poorly
  • 42. “software that matters” Building the thing right Building the right thingWhat How Misaligned requirements Poor craftsmanship Buggy and useless Hard to maintain Slow to change Does what the business needs Reliable Easy to maintain Solves the wrong problem well Solves the right problem poorly
  • 43. You don’t know what you don’t know Understanding of what needs to be delivered Time
  • 44. You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done
  • 45. You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done
  • 46. You don’t know what you don’t know Understanding of what needs to be delivered Time Requirements phase done Analysis Phase done •Our  ignorance  decreases  over  8me   •It  does  not  decrease  at  a  linear  rate   •It  does  not  always  decrease  in  a  predictable  way
  • 48. Business Goal Business Goal Business Goal “software that matters” We  start  with  a  business  goal “Increase  *cket  sales  by  5%  over  the  next  year   by  encouraging  travelers  to  fly  with  Flying  High   rather  than  with  a  rival  company.”
  • 49. Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures
  • 50. Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights
  • 51. Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights Earn  Frequent  Flyer  points  from  purchases
  • 52. Business Goal Business Goal Business Goal “software that matters” What  features  will  enable  us  to  deliver  this  goal? FeaturesFeaturesFeatures Earn  Frequent  Flyer  points  from  flights Earn  Frequent  Flyer  points  from  purchases View  Frequent  Flyer  account  balance  online
  • 53. Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples
  • 54. Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status”
  • 55. Business Goal Business Goal Business Goal “software that matters” We  use  conversa8ons  around  examples  to  build  up  our   understanding  of  these  features   FeaturesFeaturesFeatures FeaturesFeaturesExamples “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member”
  • 57. “Using examples” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
  • 58. “Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
  • 59. “Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
  • 60. “Using examples” “A  new  Frequent  Flyer  member   starts  off  with  Bronze  status” “If  she  earns  300  points,  she  becomes  a   Silver  Frequent  Flyer  member” “If  I  ask  for  the  details  about  the  flight  FH-­‐102,  I  should  see  that   it  is  a  Sydney  to  Hong  Kong  flight  that  leaves  at  11:55pm  ” •Explore  requirements   •Discover  what  we  don’t  know   •Clarify  ambigui8es   •Iden8fy  assump8ons  and  misunderstandings  
  • 61. “Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
  • 62. “Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
  • 63. “Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
  • 64. “Using examples” We  express  the  examples  in  a  structured   format  using  simple  English  phrases
  • 65. “Using examples” The  automated  acceptance  criteria   guide  the  development  process
  • 66. “Using examples” The  automated  acceptance  criteria   guide  the  development  process
  • 67. “Using examples” The  automated  acceptance  criteria   guide  the  development  process
  • 69. “Having  the  conversa/on     is  more  important  than     recording  the  conversa/on   is  more  important  than     automa/ng  the  conversa/on”   -­‐  Liz  Keogh “a shared understanding”
  • 70. BA Developer Tester Many teams build features like this… “a shared understanding”
  • 71. Story BA Developer Tester Many teams build features like this… “a shared understanding”
  • 72. Story Working   code BA Developer Tester Many teams build features like this… “a shared understanding”
  • 73. Story Working   code boring   manual   tes5ng BA Developer Tester Many teams build features like this… “a shared understanding”
  • 74. Story bug  reports Working   code boring   manual   tes5ng BA Developer Tester Many teams build features like this… “a shared understanding”
  • 75. Story bug  reports Working   code boring   manual   tes5ng WASTE BA Developer Tester Many teams build features like this… “a shared understanding”
  • 76. …but a little cooperation goes a long way… Story “a shared understanding”
  • 77. …but a little cooperation goes a long way… Story “a shared understanding”
  • 78. …but a little cooperation goes a long way… Story “a shared understanding”
  • 79. …but a little cooperation goes a long way… Story “a shared understanding”
  • 80. …but a little cooperation goes a long way… Story Examples “a shared understanding”
  • 81. …but a little cooperation goes a long way… Story Examples Automated   acceptance   criteria “a shared understanding”
  • 82. …but a little cooperation goes a long way… Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
  • 83. …but a little cooperation goes a long way… Working  code     and     Working  Automated   Acceptance  Tests Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
  • 84. …but a little cooperation goes a long way… Working  code     and     Working  Automated   Acceptance  Tests Exploratory  tes5ng,   usability  tes5ng... Shared   understanding Story Examples Automated   acceptance   criteria “a shared understanding”
  • 85. We call this “The Three Amigos” BA  and/or  product  owner Tester Developer Automatable   Acceptance   Criteria Shared   understanding “a shared understanding”
  • 86. We call this “The Three Amigos” “a shared understanding”
  • 87. We call this “The Three Amigos” “a shared understanding”
  • 88. We call this “The Three Amigos” “a shared understanding”
  • 89. We call this “The Three Amigos” “a shared understanding”
  • 90. We call this “The Three Amigos” “a shared understanding”
  • 95. Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features
  • 96. Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features Progress  repor5ng
  • 97. Living Documentation A  star5ng  point  for  manual  tests Illustrates  delivered  features Func5onal  and  technical  documenta5on Progress  repor5ng
  • 99. Automated test results tell us… How  many   tests  passed
  • 100. Automated test results tell us… How  many  failed How  many   tests  passed
  • 101. Automated test results tell us… How  many  failed How  many   tests  passed How  many  weren’t  run
  • 102. Automated test results tell us…
  • 103. Automated test results tell us… What  tests  exist  for   a  given  feature
  • 104. Automated test results tell us… What  tests  exist  for   a  given  feature How  stable  the  feature  is
  • 105. Automated test results tell us…
  • 106. Automated test results tell us… How  a  feature  was   tested
  • 107. Automated test results tell us…
  • 108. Automated test results tell us… What  a  feature  looks  like
  • 109. Automated test results tell us…
  • 110. Automated test results tell us… What  a  feature  looks  like
  • 111. Automated test results tell us… What  a  feature  looks  like
  • 112. Test results do not tell us what was not tested
  • 114. Feature Coverage What  stories  are  defined   for  this  feature?
  • 115. Feature Coverage What  stories  are  defined   for  this  feature? How  many  stories  have  automated   acceptance  criteria?
  • 116. Feature Coverage What  stories  are  defined   for  this  feature? How  many  stories  have  automated   acceptance  criteria? What  acceptance  criteria  have   been  automated?
  • 118. Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
  • 119. Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
  • 120. Business Goal Business Goal Business Goal We  can  automate  these  examples  in  the  form  of   “executable  specifica8ons” FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right”
  • 121. Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
  • 122. Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications spock RSpec “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
  • 123. Business Goal Business Goal Business Goal We  use  low-­‐level  BDD  or  TDD  tools  to  define  the   behavior  of  components,  classes  etc. FeaturesFeaturesFeatures FeaturesFeaturesExamples Low level specifications Low level specifications Low level specifications Executable specifications spock RSpec “building the software right” Low level specifications Low level specifications Low level specifications Low level specifications Low level specifications
  • 125. Acceptance  criteria  tell  us  what  we  need  to  build… “building the software right”
  • 127. What  would  we  like  the  API  to  look  like? “building the software right”
  • 128. What  would  we  like  the  API  to  look  like? “building the software right”
  • 129. What  would  we  like  the  API  to  look  like? “building the software right”
  • 131. Then  write  low-­‐level  specifica8ons  for  the  code “building the software right”
  • 132. Then  write  low-­‐level  specifica8ons  for  the  code “building the software right”
  • 134. “building the software right” These  low  level  specifica8ons  become  technical   documenta8on  for  your  APIs
  • 135. “Every class is an API for someone”
  • 137. BDD Gotchas 1 2 3 4 An8-­‐paQern  1   The  business  analyst  writes  the  scenarios  and  then  gives   them  to  the  other  team  members.
  • 139. 1 2 3 4 BDD Gotchas An8-­‐paQern  2   The  tester  writes  the  scenarios  at  the  end   to  implement  an  automated  test  suite.
  • 141. 1 2 3 4 5 BDD Gotchas An8-­‐paQern  3   The  “Three  Amigos”  sessions  don’t  result  in  usable  scenarios,  so  the   developer  invents  them  a?erwards.
  • 142. 1 2 3 4 5 BDD Gotchas An8-­‐paQern  3   The  “Three  Amigos”  sessions  don’t  result  in  usable  scenarios,  so  the   developer  invents  them  a?erwards.
  • 144. 1 2 3 4 5 BDD Gotchas An8-­‐paQern  4   The  scenarios  are  too  UI-­‐centric  or  detail-­‐focused,  and  neglect  to  express   the  core  business  value.
  • 145. 42 Benefits of BDD •Focus  effort   •Reduce  waste  and  misaligned  requirements
  • 146. 43 Benefits of BDD Deliver  more  valuable  soYware
  • 147. 44 Benefits of BDD Make  changes  safely
  • 148. 45 Benefits of BDD Faster  and  more  reliable  releases
  • 149. 46 Benefits of BDD Reduced  maintenance  costs
  • 150. BDD  requires  high  business  engagement  and  collabora8on   Adoption challenges
  • 151. BDD  works  best  in  an  Agile  or  Itera8ve  context   Adoption challenges
  • 152. BDD  does  not  work  well  in  a  silo   Adoption challenges
  • 153. Adoption challenges Skill  and  prac,ce  required:   •Wri,ng  good  scenarios  takes  prac,ce   •Poorly  wri:en  tests  can  lead  to  higher  test-­‐maintenance  costs   •Need  to  treat  test  automa,on  code  like  produc,on  code  
  • 154. In conclusion… It’s  behaviour  all  the  way  down
  • 155. Want to learn more?
  • 156. Want to learn more?
  • 157. Want to learn more? http://thucydides.info/
  • 158. Want to learn more? http://thucydides.info/ https://code.google.com/p/spock/
  • 159. Thank You John Ferguson Smart john.smart@wakaleo.com wakaleo http://www.wakaleo.com