What is Behaviour Driven Development?
Behaviour Driven Development (BDD) is similar to Test Driven Development. In BDD, B represents the behavior of the software developed. Like Test Driven Development, in Behaviour Driven Development also, the code is first written in behaviour-driven way, and further production code written. But the main difference between Behaviour Driven Development and Test Driven Development is that in BDD the test is written in understandable descriptive English type grammar.
The primary benefit of Behaviour Driven Development is that it can easily be understood by a non-technical person also. BDD implemented on those behaviors only which related to the business outcomes and too helpful in avoiding the wastage of time and resources. Basically, in BDD, the behavior is described in single notation, which increases the communication and directly understandable by domain experts, testers and developers. BDD much more focussed on collaborating with business people and on the other hand TDD seem to be too technical.
How Behaviour Driven Development (BDD) Works?
Firstly the BDD process starts with a conversation between the product owner and users, actually what they need. Further, product owner, developer, and tester collaborated and understood the requirements and based on these requirements they define the structure scenarios. Then also based on these scenarios, the developer developed the tests, and the tester uses these scenarios as the basis for their experiments.
BDD is an improvement of The Three Amigos. These three amigos are the primary views to examine an increment of work –
- Before development
- During development
- After development
#insights #bdd #framework #tdd
