BDD intro

Behavior Driven Development (BDD)

Delivering software that matters!

What it is and how we do it…


BDD (Behaviour Driven Development) is a synthesis and refinement of practices stemming from TDD (Test Driven Development) and ATDD (Acceptance Test Driven Development). BDD augments TDD and ATDD with the following tactics:

  • apply the “Five Why’s” principle to each proposed User Story, so that its purpose is clearly related to business outcomes
  • thinking “from the outside in”, in other words implement only those behaviors which contribute most directly to these business outcomes, so as to minimize waste
  • describe behaviors in a single notation which is directly accessible to domain experts, testers and developers, so as to improve communication
  • apply these techniques all the way down to the lowest levels of abstraction of the software, paying particular attention to the distribution of behavior, so that evolution remains cheap

Signs Of Use

  • A team using BDD should be able to provide a significant portion of “functional documentation” in the form of User Stories augmented with executable scenarios or examples.
  • Instead of referring to “tests”, a BDD practitioner will prefer the terms “scenario” and “specification”. As currently practiced, BDD aims to gather in a single place the specification of an outcome valuable to a user, generally using the role-feature matrix of (User Stories), as well as examples or scenarios expressed in the form given-when-then; these two notations being often considered the most readable.
  • In emphasizing the term “specification”, the intent of BDD is to provide a single answer to what many Agile teams view as separate activities: the creation of unit tests and “technical” code on one hand, the creation of functional tests and “features” on the other hand. This should lead to increased collaboration between developers, test specialists, and domain experts.
  • Rather than refer to “the unit tests of a class”, a practitioner or a team using BDD prefers to speak of “the specifications of the behavior of the class”. This reflects a greater focus on the documentary role of such specifications: their names are expected to be more expressive, and, when completed with their description in given-when-then format, to serve as technical documentation.
  • Rather than refer to “functional tests”, the preferred term will be “specifications of the product’s behavior”. The technical aspects of BDD are placed on an equal footing with techniques encouraging more effective conversation with customers, users and domain experts.
  • In addition to refactoring techniques already present in TDD, the design philosophy in BDD pays particular attention to appropriate distribution of responsibilities among classes, which leads its practitioners to emphasize “mocking”.

Expected Benefits

Teams already using TDD or ATDD may want to consider BDD for several reasons:

  • BDD offers more precise guidance on organizing the conversation between developers, testers and domain experts
  • notations originating in the BDD approach, in particular the given-when-then canvas, are closer to everyday language and have a shallower learning curve compared to those of tools such as Fit/FitNesse
  • tools targeting a BDD approach generally afford the automatic generation of technical and end user documentation from BDD “specifications”

excerpt from:

The characteristics of a good story

  • The title should describe an activity
  • The narrative should include a role, a feature and a benefit
  • The scenario title should say what’s different
  • The scenario should be described in terms of GivensEvents and Outcomes
  • The givens should define all of, and no more than, the required context
  • The event should describe the feature
  • The story should be small enough to fit in an iteration





Normally I find much more support online for Cucumber on Ruby, but here are interesting slides on using BDD with PHP and Symfony…

BDD in Symfony2 de Konstantin Kudryashov





Tips for writing better feature files



The following identifies the what & why of a feature or functionality. ie the value to the customer or the business;

As a [role]

I want [feature]

So that [benefit]

The following identifies the scenario or use case; who is the user or what are the prerequisites, the action(s) & the end result. Clear as mud!

Given [context]

When  [event]

Then  [outcome]