behavior-driven development | TechWell

behavior-driven development

Developers and testers having a conversation about behavior-driven development A Conversation about Testing within BDD

People using behavior-driven development (BDD) say conversation is the most important part of the process. They use a “given-when-then” format to describe the current state, an action that is supposed to occur, and what results to expect. But if that structure isn't working for your team, don't restrain discussion.

Justin Rohrman's picture
Justin Rohrman
Overcoming the Real Fears behind Behavior-Driven Development

Behavior-driven development can bring many benefits to software delivery. But while many companies focus on customizing frameworks, tools can only achieve as much as the people and organizations behind them. You also have to consider the individual roles and personalities of your developers and testers.

Kevin Dunne's picture
Kevin Dunne
Using Keywords to Support Behavior-Driven Development

Behavior-driven development tests can be efficiently automated with keywords, avoiding the need of a programming language and minimizing the involvement of developers. Hans Buwalda details how to support BDD scenarios with actions and keywords and switch between formats depending on your needs.

Hans Buwalda's picture
Hans Buwalda