There's a lot of hype around about BDD. Here Matt talks through the basic philosophy behind BDD, how it relates to existing agile practices, and what impact it can have on your team.
"Behaviour-Driven Development (BDD) builds upon Test-Driven Development (TDD) by formalising the good habits of the best TDD practitioners." -- The Cucumber Book, 2011
Acceptance Criteria •Must support VISA •Does not need to support MasterCard, Switch •... •Customers should be prevented from entering invalid credit card details • ... Credit Card Processing Acceptance criteria:
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid?
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid? • Can they use spaces?
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid? • Can they use spaces? • Should we checksum the digits?
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid? • Can they use spaces? • Should we checksum the digits? • How do we feed back that the details are invalid?
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid? • Can they use spaces? • Should we checksum the digits? • How do we feed back that the details are invalid?
Really? So tell me... "Customers should be prevented from entering invalid credit card details" • What exactly makes someone's credit card details invalid? • Can they use spaces? • Should we checksum the digits? • How do we feed back that the details are invalid? An example would be handy right about now...
"Customers should be prevented from entering invalid credit card details" 1. Customer enters a credit card number that contains only 15 digits 2. Customer tries to submit the form 3. form is re-displayed with an error message advising Customer that the correct number of digits is 16 For example, imagine this scenario:
"Customers should be prevented from entering invalid credit card details" 1. Customer enters a credit card number that contains only 15 digits 2. Customer tries to submit the form 3. form is re-displayed with an error message advising Customer that the correct number of digits is 16 For example, imagine this scenario: Really? Always?
"Customers should be prevented from entering invalid credit card details" 1. Customer enters a credit card number that contains only 15 digits 2. Customer tries to submit the form 3. form is re-displayed with an error message advising Customer that the correct number of digits is 16 For example, imagine this scenario: What if...? Really? Always?
# language: en Feature: Division In order to avoid silly mistakes Cashiers must be able to calculate a fraction Scenario: Regular numbers Given I have entered 3 into the calculator And I have entered 2 into the calculator When I press divide Then the result should be 1.5 on the screen
български català Cymraeg Česky dansk Deutsch English Australian LOLCAT Texan español eesti keel ຊޠ 한국어 lietuvių kalba latviešu Nederlands norsk polski português română suomi français hrvatski magyar Bahasa Indonesia italiano русский Svenska Slovensky Узбекча Tiếng Việt 简ମதจ ൟᱪதจ תירבע !"#$%&ا
OH HAI: STUFFING MISHUN: CUCUMBR I CAN HAZ IN TEH BEGINNIN "3" CUCUMBRZ WEN I EAT "2" CUCUMBRZ DEN I HAZ "2" CUCUMBERZ IN MAH BELLY AN IN TEH END "1" CUCUMBRZ KTHXBAI!
Gherkin Fundamentals Feature: Feature name Description of feature goes here Scenario: Scenario name Description of scenario goes here Given a certain context When something happens Then an outcome And something else But not this though Scenario: Another scenario name Description of another scenario goes here ...
If you're a developer • BDD will help you to focus • BDD will give you confidence to refactor • BDD will help you to understand the business-facing people on your team better
If you're a product owner or business analyst • BDD will give you a greater insight into the complexity of what you're asking for • BDD will give you transparency about what the team are doing in each iteration
If you're a product owner or business analyst • BDD will give you a greater insight into the complexity of what you're asking for • BDD will give you transparency about what the team are doing in each iteration • BDD will help your team ship faster
If you're a tester • BDD will mean you can find bugs before they've even been written • BDD will free you to do interesting, creative, exploratory testing
mattwynne
nikkei_engineer_recruiting
mtx2s
mhrtech
okamototakuyasr2
revcomm_inc
joker1007
kawagoi
mosa_siru
kgsi
achamixx
shinyaigeek
dahatake
samanthasiow
reverentgeek
tmm1
tanoku
paulrobertlloyd
jrom
chrislema
frogandcode
keavy
sonatard
cherdarchuk