BDD vs Behat
1 like2,535 views
The document discusses Behavior Driven Development (BDD) and its relationship with an open-source PHP framework called Behat. It emphasizes BDD's use of scenarios written in a ubiquitous language to create automated tests and compares imperative and declarative approaches to writing these scenarios. The content includes examples of scenarios for user actions like searching, registering, and purchasing products, highlighting best practices in BDD.
BDD vs Behat
- 1. tekst BDD vs Behat Paweł Skotnicki
- 2. About me PHP developer @ The Software House PHPers Silesia co-organizer BDD/DDD enthusiast
- 3. BDD Behaviour Driven Development Dan North, 2003 BDD is like TDD without world „test”
- 4. examples in ubiquitous language using those examples as the basis of automated tests BDD main parts
- 5. Scenarios writing down is NOT most important part conversation
- 6. Behat an open source BDD framework for PHP Gherkin language Given, When, Then
- 7. Behat !== BDD BDD = scenarios + automation Behat = automation tool
- 9. Imperative vs Declarative Imperative reusable granular steps binds to UI Declarative business language
- 13. Imperative Feature: Search In order to see a word definition As a website user I need to be able to search for a word Scenario: Searching for a page that does exist Given I am on "/wiki/Main_Page" When I fill in "search" with "Behavior Driven Development" And I press "searchButton" Then I should see "agile software development"
- 14. Feature: Search In order to see a word definition As a website user I need to be able to search for a word Scenario: Searching for a page that does exist Given there is „Behavior Driven Development” article And there is „agile software development” article When I search for "Behavior Driven Development" Then there should be "agile software development” reference Declarative
- 15. Imperative Scenario: Registering with already used e-mail Given there are following users: | username | password | email | active | | testuser1 | test1 | test@test.pl | 1 | When I am on „/register” page And I fill in „username” with „newuser” And I fill in „password” with „123456” And I fill in „email” with „test@test.pl” And I press „register” Then I should see „e-mail is already used”
- 16. Declarative Scenario: Registering with already used e-mail Given there is registered user with „test@test.pl” e-mail When I try to register with „test@test.pl” e-mail Then I should be notified that e-mail is already used
- 17. Scenario: Purchasing a product Given there is „Lightsaber” which costs $5 When I add „Lightsaber” to basket Then there should be „Lightsaber” in my basket When I check out my basket Then I should be charged for $5 Many activities
- 18. Scenario: Adding product to basket Given there is „Lightsaber” When I add „Lightsaber” to basket Then there should be „Lightsaber” in my basket Scenario: Checking out basket Given there is „Lightsaber” which costs $5 in my basket When I check out my basket Then I should be charged for $5 One activity
- 19. Tips avoid implementation details use ubiquitous language ask for examples describe one activity
- 20. Questions?
- 21. Thank you