PHPNW16 Matt Brunt - BDD & Behat
•
2 likes•1,197 views
Stories? Scenarios? BDD? Are these just more words in the ever-growing list of jargon that developers have to know? Or are they something more important than new terms to memorise? In this session we'll look at how BDD fits into the software development work-flow, how to tell user stories through features, and how to automate them in Behat. These techniques will help to ensure you're writing well designed and tested software that focuses on what the users want from a system.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to PHPNW16 Matt Brunt - BDD & Behat
Similar to PHPNW16 Matt Brunt - BDD & Behat (20)
More from Matt Brunt
More from Matt Brunt (6)
Recently uploaded
Recently uploaded (20)
PHPNW16 Matt Brunt - BDD & Behat
- 1. @TheMattBrunt BEHAVIOUR DRIVEN DEVELOPMENT & BEHAT TELLING STORIES THROUGH CODE
- 2. @TheMattBrunt Senior Software Engineer Viva IT @TheMattBrunt @PHPem
- 4. @TheMattBrunt LET’S QUICKLY TALK ABOUT TESTING
- 6. @TheMattBrunt BDD IS TDD ‘DONE RIGHT’ IT’S OFTEN SAID THAT…
- 7. @TheMattBrunt TDD IS BUILDING THE THING RIGHT
- 8. @TheMattBrunt BDD IS BUILDING THE RIGHT THING
- 10. @TheMattBrunt WE’LL BE LOOKING AT SCENARIO BDD
- 11. @TheMattBrunt BDD IS A SECOND-GENERATION, OUTSIDE-IN, PULL- BASED, MULTIPLE-STAKEHOLDER, MULTIPLE- SCALE, HIGH-AUTOMATION, AGILE METHODOLOGY. DAN NORTH http://dannorth.net/whats-in-a-story/
- 18. @TheMattBrunt HAVE CONVERSATIONS BEFORE YOU START WRITING CODE
- 19. @TheMattBrunt CAPTURE THE CONVERSATIONS SO YOU CAN USE THEM TO DRIVE DEVELOPMENT
- 20. @TheMattBrunt BDD IS THE ART OF USING EXAMPLES IN CONVERSATIONS TO ILLUSTRATE BEHAVIOUR LIZ KEOGH
- 22. @TheMattBrunt SO, HOW DO WE WORK WITH THIS?
- 25. @TheMattBrunt MULTI-LINGUAL SUPPORT TOOLS CAN INCLUDE…
- 36. @TheMattBrunt Feature: As a [role] I want [feature] So that [benefit]
- 37. @TheMattBrunt 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/
- 45. @TheMattBrunt GIVEN PUTS THE SYSTEM IN A KNOWN STATE
- 46. @TheMattBrunt WHEN DESCRIBE A KEY ACTION
- 47. @TheMattBrunt THEN DESCRIBE AN OBSERVABLE OUTCOME
- 48. @TheMattBrunt Given I have a “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
- 51. @TheMattBrunt Given I have a “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 should have a “Large T-Shirt” in my basket And the basket total should be £9.99 But I should not have tax applied to my order
- 52. @TheMattBrunt STORY STRUCTURE: THE MAKEUP OF A FEATURE FILE
- 53. @TheMattBrunt Feature: As a customer 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 should have a “Large T-Shirt” in my basket FEATURE
- 54. @TheMattBrunt SCENARIO Feature: As a customer 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 should have a “Large T-Shirt” in my basket
- 55. @TheMattBrunt STEP Feature: As a customer 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 should have a “Large T-Shirt” in my basket
- 56. @TheMattBrunt THIS IS GREAT, BUT HOW DO WE (DEVELOPERS) WORK WITH IT?
- 58. @TheMattBrunt Given I have a “Large T-Shirt” product When I add that product to my basket Then I should see that product in my basket
- 60. @TheMattBrunt
- 62. @TheMattBrunt
- 63. @TheMattBrunt
- 65. @TheMattBrunt
- 67. @TheMattBrunt BEFORE & AFTER SUITES, FEATURES, SCENARIOS, STEPS HOOKS
- 68. @TheMattBrunt
- 70. @TheMattBrunt TEST FEATURES WITH DIFFERENT CONFIGURATIONS SUITES ALLOW YOU TO…
- 71. @TheMattBrunt THEY CAN USE THE SAME FEATURE FILES. OR THEY CAN USE DIFFERENT FEATURE FILES FOR EXAMPLE:
- 72. @TheMattBrunt YOU CAN USE THE SAME FEATURE FILE TO TEST DIFFERENT IMPLEMENTATIONS WITH SUITES AND TAGS…
- 73. @TheMattBrunt
- 74. @TheMattBrunt
- 75. @TheMattBrunt YOU CAN HAVE A UI SUITE THAT USES DIFFERENT STEP DEFINITIONS THAN A SERVICE / DOMAIN / LOWER LEVEL SUITE FOR EXAMPLE:
- 76. @TheMattBrunt
- 77. @TheMattBrunt
- 78. @TheMattBrunt YOU CAN CHANGE IMPLEMENTATION WITHOUT CHANGING YOUR DOCUMENTED BUSINESS RULES WITH SUITES AND TAGS…
- 79. @TheMattBrunt THIS IS WHERE THE POWER LIES FOR ME…
- 80. @TheMattBrunt IMPLEMENTATION CHANGES MORE FREQUENTLY THAN BUSINESS RULES
- 82. @TheMattBrunt Scenario: I can add a product to my basket Given I am on the “/product/1” page When I press “Add to basket” Then I should see “Playstation 4” And I should see £250 BAD STORY
- 83. @TheMattBrunt Scenario: I can add 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 should have 1 product in my basket And the basket total should be £250 BETTER STORY
- 84. @TheMattBrunt Scenario: I can add a product to my basket Given I am on the “/product/1” page When I press “Add to basket” Then I should see “Playstation 4” And I should see £250 WHAT HAPPENS WHEN THE UI CHANGES TO SAY “ADD TO CART”?
- 88. @TheMattBrunt STORIES TOLD BY REAL WORLD EXAMPLES. USER STORIES AS REQUIREMENTS. INVOLVE MULTIPLE STAKEHOLDERS. WRITE FEATURES BEFORE CODE. WRITE FEATURES WITHOUT IMPLEMENTATION.
- 89. @TheMattBrunt BEGINNING: HAVE A CONVERSATION, CAPTURE THAT CONVERSATION MIDDLE: AUTOMATE AND IMPLEMENT THAT CONVERSATION END: HAPPY STAKEHOLDERS AND WELL BUILT SOFTWARE