QASymphony, a testing services company, has recently released the State of Test-First Methodologies 2016 Report, a survey of over 200 people/organizations from 15 countries. The purpose of the survey was to evaluate the adoption of test-first technologies -BDD/ATDD/TDD – and how they are perceived by respondents.
Behaviour-Driven Development (BDD) can help in overcoming the gap between the developer’s understanding of what needs to be built and the business’ understanding of the technical challenges caused by the requirements. The reason is improvement in communication between the two groups, Alistair Stead and Konstantin Kudryashov explains in their Beginner’s guide to BDD.
The single most important of Behaviour-Driven Development (BDD) is the conversation, not the tooling, Liz Koegh states in a presentation about 10 years of doing BDD at the recent Cucumber conference. Liz believes we have made some big mistakes during these years of practicing BDD, but she is quite excited about some of the developments over the last few years.
The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.
The Behaviour Driven Development, BDD, tool Cucumber is popular in Ruby’s TDD community. It offers a way to write tests that anybody can understand, but is any of the benefits of Cucumber really that beneficial, Kevin Liddle asks in a case against Cucumber. Jon Frisby and Matt Polito has each written a response somewhat arguing against Kevin’s ideas, both seeing benefits in using Cucumber.