Php[tek] 2016 - BDD with Behat for Beginners

https://launchkey.com
W elcom e t o
p h p [ t ek ] 2 0 1 6
R a t e Ta lk s:
https://joind.in/event/phptek-2016
Tw it t er :
#phptek
W iﬁ :
Sheraton Meetings

Session Breakdown
Preface (this)
Intro to BDD
Intro to Behat
Build some Tests
Selenium Server/Grid*
Sauce Labs*
Evolution of A Feature*
* Time permitting

Who Are You?
What is your role in the development lifecycle?
What is your experience level with PHP, Behat,
and BDD?

Pre-Run Checklist
Make sure you have:
PHP 5.5+
Composer
A browser with the Selenium driver
Selenium Server Standalone (Optional)

Create a Project
Make a project directory
Run “composer init”
Follow the prompts
For the requirements...

Add Your Requirements
1. Add the following
packages to your
project:
behat/behat
behat/mink-extension
behat/mink-goutte-driver
behat/mink-selenium2-
driver
2. Run “composer
install”

Verify Your Install
Run “vendor/bin/behat -h”
You should see the help text

Initialize Behat
Run “vendor/bin/behat --init”
Behat is initialized
Verify by running “vendor/bin/behat”

What is BDD?
BDD is business driven, user focused, and test first.
It focuses on delivering business value as effectively
and efficiently as possible while maintaining
consistent quality throughout the entire application.
BDD is a methodology built around the principles of
lean development, extreme programming, test driven
development, and domain driven design.

What BDD Provides
Better understanding of the business requirement for
development and QA
Better understanding of existing features for the
business
Better communication via a ubiquitous language
Real insight into the business effect of a defect

What It Doesn’t Provide
The answer to all your problems
A replacement for unit testing
A replacement for manual testing
Super easy to implement everywhere right this second
A measure of code quality

Failed to Assert False is True
or
How I learned to love BDD

Stay Focused
It is crucial to the success of BDD to focus on what
value a feature provides to the business.
Always understand the the role of the user and
their relationship to the feature.
Do not get distracted by the technical aspects of
the implementation.

Story BDD Hierarchy
Feature
Background
Scenario
Step Step
Scenario
Step Step

Writing Features
Applications are comprised of features
BDD discretely separates each feature
Each feature contains a narrative and a scenario
Feature may also contain a background to set the
stage for the feature scenarios

Narrative
Feature narratives are written similarly to Agile/Scrum
stories and must answer these questions:
What is the business benefit?
Who is the beneficiary?
What is the action performed?

Background
A background should contain steps common to all, or
at least most, scenarios to prepare the application
environment for the scenarios.
Background steps should be tested elsewhere as part
of another feature.
Steps failing in the background steps will identify that
the failure is not related to the feature.

Scenario
A scenarios should contain a narrative
Scenarios work in a manner similar to unit tests by arranging
the environment necessary to begin the test, perform
actions, and then assert that the expected results have been
attained
Scenarios should not test multiple features. Do not perform
actions after assertions.

Scenario Outline
Scenario outlines use a common set of steps with
placeholders for data provided in a data table.
They are a replacement for multiple scenarios in which
data is the only differentiator and does not define the
feature. Adding sales tax would be an example of a
feature in which the data in the action and assertion
would be different.

Step
Steps do one of the following:
Arrange the environment
Perform an action
Assert a result of the previous actions
Steps should be reasonably reusable
Steps should be aggregated for simplification when
arranging the environment

What is Behat?
Open source Behavior Driven Development
framework for PHP
Official PHP implementation of Cucumber
One of the easiest Cucumber implementations to
get up and running quickly
Good documentation: http://docs.behat.org

Installation
PHAR installation
Single global install
One version for feature contexts
Project Installation
Composer based install as dependency
Version and dependencies tied to project

Components
Command line executable – behat
Configuration file – behat.yml
Feature context(s)
Feature Files

CLI Executable
Allows for initializing the environment
Running features
Features and scenarios filterable by tags
Chooses environment
Listing step definitions

Configuration File
Split up into profiles
(inherit from default)
Configures custom
autoloader path
Defines global tag filters
Defines output
formatters
Defines feature suites
Configures extensions

Feature Context
Defines steps
May extend other contexts
May access other contexts
May add hooks for pre/post tag, step, scenario,
feature, and suite execution.

Gherkin
Gherkin is a Domain Specific Language (DSL)
utilized to write Features in Behat. It uses key words
to identify the type of step:
Given – Arrange
When – Act
Then - Assert

Example Gherkin
Feature: Home Page
Scenario: Login Link
Given I am on the homepage
When I click " Login"
Then I will be on the "LaunchKey | Log in" page

Step Backing Code
Method on a feature context
Contains doc block annotated (@) matchers
Support defined in context. Defaults to Turnip
Supports Turnip and regular expressions
Can contain examples doc block
Can contain descript in the doc block

Example Step
/**
* Opens homepage
* Example: Given I am on "/"
* Example: When I go to "/"
* Example: And I go to "/”
* @Given (I )am on :path
* @When (I )go to :path
*/
public function visitPath($path)
{
$this->browser->open($path);
}

Let’s Get Coding!
Make sure you have:
PHP 5.5+
Composer
A browser with the Selenium driver
Selenium Server Standalone

Add Requirements
1. Add the following
packages to your project:
behat/behat
behat/mink-extension
behat/mink-goutte-driver
behat/mink-selenium2-
driver
2. Run “composer install”

Verify Your Install
Run “vendor/bin/behat –h”
You should see the help text

Configure Mink
default:
extensions:
BehatMinkExtension:
base_url: http://adam-bdd-with-behat.ngrok.io
goutte: ~
selenium2: ~

Add Contexts
default:
suites:
default:
contexts:
- BehatMinkExtensionContextMinkContext
- FeatureContext

Verify Configuration
Run “vendor/bin/behat –dl”
You should see a LOT of steps
Run “vendor/bin/behat –di”
You should see additional information for the
steps

Lets Write A Feature
Requirement:
In order to use the site
As a site visitor
I can access the website

Let’s Check Your Work
How did you word your narrative?
How did you word your scenario?
Did you use existing steps or do you need new
steps?

Let’s Make Another
Requirement:
In order to be a user
As a visitor
I can register for a user account

Add Requirements
E-Mail Address is the user identifier and must be
unique among all users
Name is required and captures the users name
Password is required and must utilize a verification
field to ensure correct password entry

Let’s Check Your Work
How did you word your narrative?
How did you word your scenarios?
Did you use existing steps or do you need new
steps?
Did you clean up after yourself.

Finish Up Labs
Server and Behat features found in GitHub:
https://github.com/aenglander/bdd-with-behat-for-
beginners
Master branch is Behat
Master is tagged to go step by step
Server branch is server

Selenium
Industry standard
Server with remote API
Direct integration with Behat/Mink via Selenium
Driver
Can be used headless with PhantomJS via
GhostDriver implementation

Using Selenium Server
Add config to bahat.yml and specify browser
BehatMinkExtension:
browser_name: chrome
goutte: ~
selenium2: ~
Apply @javascript tag to scenarios or a feature
Start Selenium Standalone Server
Run “vendor/bin/behat”

Selenium Review
Were you able to get your server running?
Did your tests pass?
Any questions regarding Selenium Server?

Selenium Grid
Allows for multiple simultaneous test runs, multiple
browser versions, and multiple operating systems
One Hub and Multiple Nodes
Uses same app as Standalone Server
Can be flakey and hard to manage

Selenium Grid Example
Start hub:
selenium-server-standalone –role hub
Start nodes
selenium-server-standalone –role node –hub URL
Set the wd_host under selenium2 in behat.yml

Hosted Selenium
Special Drivers for Sauce Labs and
BrowserStack
Not well documented but work very well
Allow for a “Grid” style environment without
managing the Grid

Configuring Mink Driver
Poorly documented
Easy to figure out the settings by looking at the
driver factories. See:
vendor/behat/mink-
extension/src/Behat/MinkExtension/ServiceContainer
/Driver

Best Practices
Feature files contain one Feature
Features should be more business than technical focused
Use the three A’s
Arrange – Background – Given
Act – When
Assert - Then

Best Practices (cont.)
Make steps visually verifiable. Feature files
should be able to serve as documentation
Clean up after yourself
Scenarios should be idempotent
Spend the time to do it the right way

Evolution of a Feature

Business Owner
Brings a very general idea as a requirement.
Hopefully they have an idea of business priority
and impact.
This general idea is represented as a product
backlog item

From: Big Boss
To: Project Manager
Proj,
We need a TODO list ASAP! This is top priority. Could
mean billions in revenue. Get me an estimate tomorrow!
Big

Scrum Master/BSA
Works with the business owner to flesh out
requirements.
Requirements are very general and generic.
They are only used to determine scope and
assist with sizing during sprint planning.

TODO list
In order to keep on track with tasks, as a user, I can
manage my tasks in a TODO list. This will be
accomplished by adding tasks to a task list and being
able to update the completion status of those tasks.

Developer
Defines the actual user experience
Takes the very generic business requirements
and creates very specific scenarios for each
feature
Scenarios are analogous to use cases

Feature: Task List
As an application user, in order to see my tasks, I will be presented a
ask list.
Scenario: No pre-existing tasks
As a user with no existing tasks, I will see an input field with a
placeholder value of “What needs to be done”. The footer will not be
visible.
Scenario: Pre-existing tasks
As a user with pre-existing tasks, I will see the task input fields and
below it a list of tasks in the order in which they were entered.

Test Automation
Takes the User Experience requirements and
builds “feature” files utilizing Gherkin, the
Cucumber DSL for writing test scenarios
Scenarios will be standardized to promote
ubiquitous language conformity and step definition
re-use
Missing step definitions identified

Feature: Task List
As an application user, in order to see my tasks, I will be presented a task
list.
Background:
Given I am on the homepage
Scenario: Pre-existing tasks shows list
Given the “Do first” task exists
And the “Do next” task exists
Then the “Do first” task is the first item in the task list
And the “Do next” task is the second item in the task list

Feature Acceptance
The Feature files with their scenarios act as acceptance
criteria for development
Once the tests pass, the story is considered complete and
ready for demo to the product owner.
Any features/scenarios that cannot be immediately tested in
automation are tagged as such but are added regardless.

Please Rate This Talk
https://joind.in/talk/834ba

adam@launchkey.com
adam_englander on Twitter
#aenglander on Freenode
aenglander on GitHub
https://github.com/aenglander/bdd-with-behat-for-
beginners
https://joind.in/talk/834ba

Php[tek] 2016 - BDD with Behat for Beginners

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Php[tek] 2016 - BDD with Behat for Beginners

Similar a Php[tek] 2016 - BDD with Behat for Beginners (20)

Más de Adam Englander

Más de Adam Englander (20)

Último

Último (20)

Php[tek] 2016 - BDD with Behat for Beginners

Notas del editor