Consultant, coach, trainer, analyst, and developer for over 30 years.
Seb has been involved in the full development lifecycle with experience that ranges from architecture to support, from BASIC to Ruby. He’s a BDD advocate with SmartBear, helping people integrate all three practices of BDD into their development process and ensuring that appropriate tool support is available.
Regular speaker at conferences and occasional contributor to software journals. Co-author of the BDD Books series "Discovery” and "Formulation" (Leanpub), lead author of “The Cucumber for Java Book” (Pragmatic Programmers)", and contributing author to “97 Things Every Programmer Should Know” (O’Reilly). He blogs at cucumber.io/blog and tweets as @sebrose.
Living Documentation – Pot of Gold at the End of the BDD Rainbow
Living Documentation is documentation that automatically notifies the team when it's out-of-date or incorrect. And it comes for free when you follow the Behavior-Driven Development (BDD) approach.
If there is one thing that the agile community has learned over the past twenty years, it's that user stories on their own are insufficient to specify, document, and validate a product. BDD is a non-dogmatic approach that brings the business and delivery teams closer together by adopting three core practices: Discovery, Formulation, Automation. Together, these practices build on existing agile methods to support rapid feedback, reduced rework, joyful teams, and satisfied customers.
In this session we'll explore what BDD is, the complementary relationship between BDD and Test Automation, and why every team should aspire to having Living Documentation.
Disclaimer - no pixies, faeries, elves, or unicorns were used in the making of this presentation.
Describe the core practices of BDD
Explain what Living Documentation is
Identify the risks to their projects that Living Documentation could mitigate