Agile2012

Behavior Driven Development helps business and development teams to communicate, through collaborative writing of examples of how a system will behave. Nowadays frameworks like Cucumber and JBehave exist which allow those scenarios to be written in English - but what would you do if they weren't there? We look at strategies for writing small, readable domain-specific languages on top of ordinary TDD frameworks like NUnit and JUnit, and show how to structure the underlying steps to keep scenarios maintainable - lessons which can be applied to all scenarios, even with frameworks. We also look at the costs of using frameworks, alongside the benefits, and how to know when to use them - and when to step away from the tools.