There was the challenge from @refractalize:
BDD starts out as "tests are specs" now it's "full stack methodology" wondering where it will stop! :)
Which resulted in Dan's twitter pitch:
#BDD: 1. Enough is enough - there's a diminishing return on all activities so let pull (demand) dictate the flow
#BDD: 2. Deliver stakeholder value (acknowledge the non-business stakeholders)
#BDD: 3. It's all behaviour. Code level (specs/examples/tests), app level (scenarios), org level (sys integration)
For the more formal here is Dan's definition from the "Agile Specifications, BDD and Testing eXchange", Nov. 2009:
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.
Want more? Check out the latest interview with Dan on InfoQ and his great presentation: Behaviour-Driven Development - a road to effective design and clean code.
No comments:
Post a Comment