Belief that process problems can be solved by installing a tool
Belief that business users should write acceptance tests
Belief that tests are either unit of acceptance-integration
<insert role> should do BDD in isolation (eg testers do everything)
Belief that the long term value of BDD is in regression testing
What BDD is not?
It is really BDD?
FALSE: BDD is a framework
FALSE: BDD is for defining system behavior
FALSE: BDD is for Business Applications
FALSE: BDD frameworks are for higher level, TDD for lower level components
FALSE: BDD frameworks are for end users to use
FALSE: BDD is for Integration Testing, TDD is Unit Testing
So, what the f**k is BDD?
Dan’s definition of BDD
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.