There is much buzz about Behat in the developer community. We’ve learned that automated behaviour testing is a highly valued component of our projects. But there are many tools available and many choices for implementing a BDD framework. In this session we make the case that Behat is the right choice for a Drupal project. We intend to persuade you why Behat is a step in the right direction by looking at code example, showing demos, and discussing the advantages and disadvantages of the options available.

Given you want to test your site
And you've heard the buzz about Behat
When you attend this session
And learn how to make the most of testing
And you apply this to your project
Then you will have no bugs on your site*

Topics covered:

1. Quick intro to Behaviour Driven Development.
2. Setting up your Drupal project for Behat Testing including Mink, Selenium, Drupal Extension.
3. Choosing a web driver for scenarios.
4. When to use Behat and when not to use it.
5. Role based or permissions based test users.
6. Dealing with file uploads, pathauto and other fun points.

We'll discuss these questions:

1. Do non-programmers actually ever read the gherkin code?
2. Why not just use Selenium, or some other testing framework?
3. Behat for testing core, contrib modules?
4. Can you use Behat for UAT?

Comparison of tools:

1. SimpleTest, PHPUnit (not able to do BDD)
2. Selenium
3. Codeception
4. jMeter
5. Behat

The case for Behat:

1. Using Behat for User Acceptance Tests
2. Simple to read and write scenarios
3. Flexible implementation
4. Drupal extension
5. Community momentum

* In theory. And also come learn why this is a bad test scenario.