Every new feature added to your project and bug report filed against it has background and context. Keeping the relevant context in your project is important for future developers (including yourself) but it's not always easy to include without lengthy comment blocks. Tests provide a mechanism to write the context with code, but most non-developers will not understand what you have written without plain ol' words to explain it. Stories bridge the gap between developers and non-developers, and using a testing framework called Behat, you can become an expert storyteller while drastically improving the amount of relevant information in your project and the quality and quantity of automated, repeatable tests to prove your code behaves as intended. At the end of this session you will have gained an understanding of the components of a good user story, how to adapt the story to steps for use with the Gherkin DSL, and how to automatically run these story tests as you drive development of a feature using Behat.