Download as PDF, PPTX
![@Brunty
Feature:
As a [role]
I want [feature]
So that [benefit]](https://image.slidesharecdn.com/bddbehatforphpsw-170309095740/85/BDD-Behat-35-320.jpg)
![@Brunty
Feature:
In order to [achieve value]
As a [role]
I want [feature]
https://lizkeogh.com/2008/05/14/rip-as-a-i-want-so-that/](https://image.slidesharecdn.com/bddbehatforphpsw-170309095740/85/BDD-Behat-36-320.jpg)
Uploaded byMatt Brunt
BDD & Behat
The document discusses Behavior Driven Development (BDD) as an agile methodology that emphasizes conversations among multiple stakeholders to ensure the right features are built. It highlights the importance of writing user stories in a Gherkin format, providing a structured approach to define features and scenarios. The content underscores the need for collaboration before coding, capturing conversations to drive development and ultimately create better software outcomes.
More Related Content
![BDD: Telling stories through code [For TechNotts]](https://cdn.slidesharecdn.com/ss_thumbnails/bdd-fromstorytocodefortechnotts-160105000630-thumbnail.jpg?width=640&height=640&fit=bounds)
BDD & Behat
- 1. @Brunty BEHAVIOUR DRIVEN DEVELOPMENT &BEHAT TELLING STORIES THROUGH CODE
- 2. @Brunty Senior Software Engineer VivaIT @Brunty @PHPem
- 3.
- 4.
- 5. @Brunty BDD IS TDD‘DONE RIGHT’ IT’S OFTEN SAID THAT…
- 6. @Brunty TDD IS BUILDING THETHING RIGHT
- 7. @Brunty BDD IS BUILDING THERIGHT THING
- 8.
- 9. @Brunty WE’LL BE LOOKING ATSCENARIO BDD
- 10. @Brunty BDD IS ASECOND-GENERATION, OUTSIDE-IN, PULL- BASED, MULTIPLE-STAKEHOLDER, MULTIPLE- SCALE, HIGH-AUTOMATION, AGILE METHODOLOGY. DAN NORTH http://dannorth.net/whats-in-a-story/
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. @Brunty HAVE CONVERSATIONS BEFORE YOUSTART WRITING CODE
- 18. @Brunty CAPTURE THE CONVERSATIONS SOYOU CAN USE THEM TO DRIVE DEVELOPMENT
- 19.
- 20.
- 21. @Brunty SO, HOW DOWE WORK WITH THIS?
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35. @Brunty Feature: As a [role] Iwant [feature] So that [benefit]
- 36. @Brunty Feature: In order to[achieve value] As a [role] I want [feature] https://lizkeogh.com/2008/05/14/rip-as-a-i-want-so-that/
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. @Brunty GIVEN PUTS THE SYSTEMIN A KNOWN STATE
- 45.
- 46.
- 47. @Brunty Given I havea “Large T-Shirt” product When I add a “Large T-Shirt” to my basket Then I should have a “Large T-Shirt” in my basket
- 48.
- 49.
- 50. @Brunty Given I havea “Large T-Shirt” product that costs £9.99 And I have an empty basket And I am a tax-exempt customer When I add a “Large T-Shirt” to my basket Then I have a “Large T-Shirt” in my basket And the basket total should be £9.99 But I do not have tax applied to my order
- 51. @Brunty STORY STRUCTURE: THE MAKEUPOF A FEATURE FILE
- 52. @Brunty Feature: As acustomer I want to be able to add products to my basket So that I can have a gift for my partner Scenario: I can add a product to the basket Given I have a "Large T-Shirt" product When I add a “Large T-Shirt” to my basket Then I have a “Large T-Shirt” in my basket FEATURE
- 53. @Brunty SCENARIO Feature: As acustomer I want to be able to add products to my basket So that I can have a gift for my partner Scenario: I can add a product to the basket Given I have a "Large T-Shirt" product When I add a “Large T-Shirt” to my basket Then I have a “Large T-Shirt” in my basket
- 54. @Brunty STEP Feature: As acustomer I want to be able to add products to my basket So that I can have a gift for my partner Scenario: I can add a product to the basket Given I have a "Large T-Shirt" product When I add a “Large T-Shirt” to my basket Then I have a “Large T-Shirt” in my basket
- 55. @Brunty HOW DO DEVELOPERS WORKWITH IT?
- 56.
- 57. @Brunty Given I havea "Large T-Shirt" product When I add a “Large T-Shirt” to my basket Then I have a “Large T-Shirt” in my basket
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66. @Brunty BEFORE & AFTERSUITES, FEATURES, SCENARIOS, STEPS HOOKS
- 67.
- 68.
- 69. @Brunty TEST FEATURES WITH DIFFERENTCONFIGURATIONS SUITES ALLOW YOU TO…
- 70. @Brunty SUITES CAN USETHE SAME FEATURE FILES. OR SUITES CAN USE DIFFERENT FEATURE FILES FOR EXAMPLE:
- 71. @Brunty YOU CAN USETHE SAME FEATURE FILE TO TEST DIFFERENT IMPLEMENTATIONS WITH SUITES AND TAGS…
- 72.
- 73.
- 74. @Brunty YOU CAN HAVEA UI SUITE THAT USES DIFFERENT STEP DEFINITIONS THAN A SERVICE / DOMAIN / LOWER LEVEL SUITE FOR EXAMPLE:
- 75.
- 76.
- 77. @Brunty YOU CAN CHANGEIMPLEMENTATION WITHOUT CHANGING YOUR DOCUMENTED BUSINESS RULES WITH SUITES AND TAGS…
- 78. @Brunty THIS IS WHERETHE POWER LIES I FIND…
- 79. @Brunty IMPLEMENTATION CHANGES MORE FREQUENTLYTHAN BUSINESS RULES
- 80.
- 81. @Brunty Scenario: I canadd a product to my basket Given I am on the “/product/1” page When I press “Add to basket” Then I will see “Playstation 4” And I will see £250
- 82. @Brunty Scenario: I canadd a single product to my basket Given I have a “Playstation 4” that costs £250 When I add the “Playstation 4” to my basket Then I will have 1 product in my basket And the basket total will be £250 BETTER STORY
- 83. @Brunty Scenario: I canadd a product to my basket Given I am on the “/product/1” page When I press “Add to basket” Then I will see “Playstation 4” And I will see £250 WHAT HAPPENS WHEN THE UI CHANGES TO SAY “ADD TO CART”?
- 84.
- 85.
- 86.
- 87.
- 88. @Brunty STORIES TOLD BYREAL WORLD EXAMPLES. USER STORIES AS REQUIREMENTS. INVOLVE MULTIPLE STAKEHOLDERS. WRITE FEATURES BEFORE CODE. WRITE FEATURES WITHOUT IMPLEMENTATION.
- 89. @Brunty BEGINNING: HAVE A CONVERSATION,CAPTURE THAT CONVERSATION MIDDLE: AUTOMATE AND IMPLEMENT THAT CONVERSATION END: HAPPY STAKEHOLDERS AND WELL BUILT SOFTWARE
- 90.
- 91.
- 92.