BDD & Behat for Glasgow PHP
•
1 like•482 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 what makes a good feature file. These techniques will help to ensure you're writing well designed and tested software that focuses on what the users really want from a system.
Recommended
More Related Content
Similar to BDD & Behat for Glasgow PHP
Similar to BDD & Behat for Glasgow PHP (20)
More from Matt Brunt
More from Matt Brunt (9)
Recently uploaded
Recently uploaded (20)
BDD & Behat for Glasgow PHP
- 1. @Brunty BEHAVIOUR DRIVEN DEVELOPMENT & BEHAT TELLING STORIES THROUGH CODE
- 2. @Brunty Senior Software Engineer Viva IT @Brunty @PHPem
- 3. @Brunty BEFORE WE TALK ABOUT BDD
- 5. @Brunty BDD IS TDD ‘DONE RIGHT’ IT’S OFTEN SAID THAT…
- 6. @Brunty TDD IS BUILDING THE THING RIGHT
- 7. @Brunty BDD IS BUILDING THE RIGHT THING
- 8. @Brunty WE’LL BE LOOKING AT SCENARIO BDD
- 9. @Brunty 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/
- 16. @Brunty HAVE CONVERSATIONS BEFORE YOU START WRITING CODE
- 17. @Brunty CAPTURE THE CONVERSATIONS SO YOU CAN USE THEM TO DRIVE DEVELOPMENT
- 22. @Brunty MULTI-LINGUAL SUPPORT TOOLS CAN INCLUDE…
- 30. WHEN WRITING STORIES ▸ Be descriptive ▸ Use real-world examples ▸ Describe the business logic ▸ Give context
- 32. @Brunty Feature: As a [role] I want [feature] So that [benefit]
- 33. @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/
- 39. @Brunty GIVEN PUTS THE SYSTEM IN A KNOWN STATE
- 40. @Brunty WHEN DESCRIBE A KEY ACTION
- 41. @Brunty THEN DESCRIBE AN OBSERVABLE OUTCOME
- 42. @Brunty 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
- 45. @Brunty 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 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
- 46. @Brunty STORY STRUCTURE: THE MAKEUP OF A FEATURE FILE
- 47. @Brunty 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 have a “Large T-Shirt” in my basket FEATURE
- 48. @Brunty 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 have a “Large T-Shirt” in my basket
- 49. @Brunty 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 have a “Large T-Shirt” in my basket
- 50. @Brunty HOW DO DEVELOPERS WORK WITH IT?
- 52. @Brunty 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
- 56. @Brunty
- 57. @Brunty
- 58. @Brunty TAGS
- 59. @Brunty
- 60. @Brunty HOOKS
- 61. @Brunty BEFORE & AFTER SUITES, FEATURES, SCENARIOS, STEPS HOOKS
- 62. @Brunty
- 64. @Brunty TEST FEATURES WITH DIFFERENT CONFIGURATIONS SUITES ALLOW YOU TO…
- 65. @Brunty SUITES CAN USE THE SAME FEATURE FILES. OR SUITES CAN USE DIFFERENT FEATURE FILES FOR EXAMPLE:
- 66. @Brunty YOU CAN USE THE SAME FEATURE FILE TO TEST DIFFERENT IMPLEMENTATIONS WITH SUITES AND TAGS…
- 67. @Brunty
- 68. @Brunty
- 69. @Brunty YOU CAN HAVE A UI SUITE THAT USES DIFFERENT STEP DEFINITIONS THAN A SERVICE / DOMAIN / LOWER LEVEL SUITE FOR EXAMPLE:
- 70. @Brunty
- 71. @Brunty
- 72. @Brunty YOU CAN CHANGE IMPLEMENTATION WITHOUT CHANGING YOUR DOCUMENTED BUSINESS RULES WITH SUITES AND TAGS…
- 73. @Brunty THIS IS WHERE THE POWER LIES I FIND…
- 74. @Brunty IMPLEMENTATION CHANGES MORE FREQUENTLY THAN BUSINESS RULES
- 76. @Brunty 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 will see “Playstation 4” And I will see £250
- 77. @Brunty 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 will have 1 product in my basket And the basket total will be £250 BETTER STORY
- 78. @Brunty 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 will see “Playstation 4” And I will see £250 WHAT HAPPENS WHEN THE UI CHANGES TO SAY “ADD TO CART”?
- 83. @Brunty STORIES TOLD BY REAL WORLD EXAMPLES. USER STORIES AS REQUIREMENTS. INVOLVE MULTIPLE STAKEHOLDERS. WRITE FEATURES BEFORE CODE. WRITE FEATURES WITHOUT IMPLEMENTATION.
- 84. @Brunty BEGINNING: HAVE A CONVERSATION, CAPTURE THAT CONVERSATION MIDDLE: AUTOMATE AND IMPLEMENT THAT CONVERSATION END: HAPPY STAKEHOLDERS AND WELL BUILT SOFTWARE