Agile2011

BDD helps development teams hold conversations about the behaviour of their system with non-technical stakeholders. BDD has changed from its early roots as a replacement to TDD and now encompasses Feature Injection, extending across the whole software lifecycle. In this tutorial we look at the original reasons for BDD, returning the focus to the language and conversations at its heart. We look at how BDD’s patterns can be applied at multiple scales, from the initial project vision all the way to the code, to deliberately discover and address ignorance in every aspect of software development.