{"id":59,"date":"2011-03-04T09:21:00","date_gmt":"2011-03-04T09:21:00","guid":{"rendered":"https:\/\/wdev-blog.azurewebsites.net\/index.php\/2011\/03\/04\/behavior-driven-development\/"},"modified":"2011-03-04T09:21:00","modified_gmt":"2011-03-04T09:21:00","slug":"behavior-driven-development","status":"publish","type":"post","link":"http:\/\/panahy.nl\/index.php\/2011\/03\/04\/behavior-driven-development\/","title":{"rendered":"Behavior Driven Development"},"content":{"rendered":"

Dan North in his blog <\/a>about Behavior Driven Development write the following:<\/p>\n

<\/div>\n
“ If we could develop a consistent vocabulary for analysts, testers, developers, and the business, then we would be well on the way to eliminating some of the ambiguity and miscommunication that occur when technical people talk to business people.<\/span>“<\/div>\n
He describes BDD as follows:<\/div>\n
<\/div>\n
“BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters.<\/span>“<\/div>\n
<\/div>\n
<\/p>\n

The practices of BDD include:<\/p>\n