BDD with Behat and PHPSpec
Download as PPTX, PDF0 likes450 views
This document discusses Behavior-Driven Development (BDD) using Behat and provides examples of how to write feature files and scenarios. It outlines the standard BDD format including features, scenarios, and backgrounds. It also shows how to write scenarios using the Given/When/Then format and includes tables for scenario results. Finally, it briefly mentions PHPSpec for unit testing and provides links for further information.
BDD with Behat and PHPSpec
- 1. BDD with Behat Rob Ingram
- 2. Image credit: J Williams
- 4. Outline In order to <achieve a business goal> As a <stakeholder> I want <something>
- 5. Outline Feature: store locator In order to shop at the closest store As a customer I want to search for stores in my city
- 6. Alternative format Feature: store locator As a customer I want to search for stores in my city So that I can shop at the closest store
- 7. Scenario Given <a context> When <something happens> Then <I expect some outcomes>
- 8. Scenario Scenario: search by city name Given I am on the homepage When I fill in "location" with "Christchurch" And I press "Locate" Then I should be on the “Store Locator” page And I should see “Kathmandu Christchurch CBD Re:START” And I should see “0.2km”
- 9. Scenario Scenario: search by city name Given I am on the homepage When I fill in "location" with "Christchurch" And I press “Locate" Then I should be on the “Store Locator” page And I should see the following store results: | name | distance | | Kathmandu Christchurch CBD Re:START | 0.2km | | Kathmandu Tower Junction | 2.5km |
- 10. Background Background: Given I am logged in
- 13. PHPSpec <?php namespace spec; use PhpSpecObjectBehavior; class MarkdownSpec extends ObjectBehavior { function it_converts_plain_text_to_html_paragraphs() { $this->toHtml("Hi, there")->shouldReturn("<p>Hi, there</p>"); } }
- 17. Links Behat: http://docs.behat.org/en/v3.0/ Behat Silverstripe: https://github.com/silverstripe- labs/silverstripe-behat-extension PHPSpec: http://www.phpspec.net/en/stable/
Editor's Notes
- #3: 1. What is BDD - Extension of TDD to cover the entire development process - Associated with agile methodologies - Encourage a collaborative process with all stakeholders - Requirements generated by cross-functional teams, BA, developers, tester involved early on - shared understanding 2. "Build the software right", "Build the right software" - Each proposed feature should have a specific business value that everyone involved buys into - Examples produced in a standard format that can be understood by everyone - This is an _executable specifications_ - And living documentation of the behaviour of the system that is PROVEN 3. Language of the spec is often referred to as Gherkin - Best know through Ruby tool Cucumber - TDD actually came out of the Java community (JBehave) - All stories/features refer to a user (persona?) and the business value of the feature to that user - Stories are the basis for discussion in an iterative process
- #4: At least a outline (high level) and number of scenarios (detail of what happens) Optional narrative and background
- #5: 2 usual formats for outline
- #8: All of these can be extended with “And”
- #9: Each line is a “step”
- #11: Set up conditions to be executed before each scenario
- #12: Beat - PHP version of a suite of tools Drives the site as a user would. Goutte driver, Selenium or headless for JS Each line becomes a step in a context file Executes known steps Provides outline for any unknown tests Match regexp Mink - common web steps and helpers
- #13: When a feature fails, if it requires logic, drop down to standard TDD process then back up once green
- #16: SS behat extension - Access SS classes from Behat context - Set up and reset test database - YAML fixtures in Behat scenarios
- #17: DB JS/AJAX timing Slow, especially when driving a browser for JS Targeting HTML elements - temptation to be too imperative rather than declarative