Member-only story
That is how the developer should behave inside BDD
In BDD, Behavior Driven Development, the Developer is the cornerstone.
It is amazing how the obvious is often overlooked. For example, some time ago I was in the middle of the typical discussion if with TDD we have to test all the public methods, or also the private methods. This question has no sense, it is like asking what is at the north of the North Pole. I did not know how to explain it, until one day, I just find the plain truth: In TDD there are no methods before writing the test; methods exists because the test. The discussion ended that day.
The same happened with BDD. For some reason, QA teams tend to appropriate the BDD workflows and focus all the process in testing, they neglect the development. But BDD does not focus on testing or quality, its own name says Behavior Driven Development: it focuses on development. Ok, behaviors are a synonym for test, but they drive the development, so the final user of the BDD are the developers.
Rule 1: Take ownership of BDD
So, the first rule for developers is to take ownership of the BDD. If you are the developer, you are the responsible. You have to realize that the best person to understand and guide BDD is you. You know the code, you know the development, you know…
