Behavior Driven Development(BDD)

BDD was developed by Dan North and according to The RSpec book BDD “is about implementing an application by describing its behavior from the perspective of its stakeholders.”  It is based on TDD or Test Driven Development. And one of the purposes of BDD is to understand the problem from the point of view of the stakeholders, so in this way we will write software that matter, software that satisfies our client expectation.

There are 3 principles of BDD:

1. Enough is enough: This is all about doing what we have to do and anything else, because it could be a waste of effort.
2. Deliver stakeholder value: Everything should produce value, if it doesn’t produce it, don’t do it
3. It’s all behavior: This is because BDD focus on behavior instead of structure.

     So I can say that the main purpose of BDD is to minimize the communication’s problems that are in almost every project. In BDD exists a triad that includes the words: Given, When and Then.

BDD consists of writing stories and derivate these stories into scenarios.  For example in the book that I mentioned earlier they explain that there is a cycle in BDD which is:

Basically following this cycle we will be applying correctly BDD. In another post I’m going to show how to write user stories and scenarios.

Bibliography

Chelimsky, D. (2010). The RSpec Book. The Pragmatic Bookshelf.