1.
Behavior Driven Development: Bridging the Gap in
Communication While Scaling Your Testing Efforts
Have you ever had that problem where the tester finds a bug and the developer says it
is working as expected? When you raise the issue, the product owner says something like
"Hmm. I never thought of that before. That's a good point." Now the team has to go
back to reimplement and test the feature.
This type of situation generally occurs when there is a lack of collaboration and
communication on the team. If the team had gotten together and discussed behaviors
with examples, the problem of finding this issue after implementation could have been
avoided. This does not mean to say that the best communicators and collaborators will
be free of the issue though. The problem arises when working with spoken and written
words, especially in English. When working with language and communication, there is
always ambiguity. This ambiguity can be limited by working through examples and
speaking with the team about the meaning of the feature that needs to be
implemented.
One approach that can be used to help with this scenario is to use a process called
Behavior Driven Development (BDD). In the rest of this ebook, we're going to go over
how to reduce ambiguity and limit rework. We'll also look at some examples using a
BDD tool called HipTest and show how it can make the BDD process easier and more
effective with Continuous Testing.
