Recently I've heard a lot about Behaviour-Driver Development (BDD) and three amigos essential to make it work. These include: the business, the developer, and the tester.

According to the Angie Jones article, it is difficult to actually successfully implement BDD, especially when it comes to bringing on-board the business and developers itself. There is no surprise that testers after weeks, months or even years give up on implementing the BDD structure into their workplace and solely focus on one side of it, which are executable test scenarios. As Angie Jones mentioned, BDD testing frameworks (including for example, Cucumber, Specflow, etc.) can function for its sole purpose of test automation, and can be somewhat successful.

The whole article highlights that a lot of testers are put under pressure when they are “not really doing BDD”, however they have a lot of knowledge of how BDD should actually work and look. The issue is on another level when the rest of the team is not keen to be involved and collaborate with the testing team to make necessary changes.

Whereas, it is incredibly important that testing frameworks are able to work without the BDD being fully adopted, it is vital for the team to cooperate and introduce changes if they are needed to improve the product and the business.

And once again, this highlights the importance of appropriate and effective communication between testers, developers and the business itself.