A practical blog on how to write Scenarios using BDD
from Ryan McKergow: BDD aims to explain the behavior of a system in easy to understand language. Using BDD and Scenarios allows requirements and tests to utilize the same approach in documenting system behavior. The format is fairly simple, but sometimes hard to get your head around how to write in this format. This is why I’m aiming to explain in practical terms how it works, so that you can either begin using it or get a refresher on BDD.
Using “Given-When-Then” to Discover and Validate Requirements
from Mary Gorman and Ellen Gottesdiener: Here we summarize the technique of Given-When-Then (GWT). It is a structured format for expressing scenarios with example data, including pre- and post-conditions, helping project stakeholders (business, customer and technology partners) communicate using business domain language. You can use GWT to explore product options and confirm selected options in a concrete, tangible way. Often called “specification by example,” GWT provides living documentation for your delivered product. It simultaneously specifies requirements while identifying acceptance tests, thereby streamlining discovery and delivery.