|3 hours||*hands on||practitioner level|
Find the missing link. Teams working in an Agile/Scrum environment commonly use Stories to track and prioritize feature requirements. But given an individual Story, how do you know when you are done with it?
- When is coding finished?
- When does testing start?
- When is it coded & tested?
- Coded, tested and deployed?
- Coded, tested, deployed and verified by the Customer?
Enter “Executable Specifications”. Creating acceptance criteria for a Story tells you where to start and when to stop. Automating them allows you to regularly test that nothing has broken. Executable Specifications are the missing glue that ties the pipeline together.
Unfortunately, getting this right is tricky and, more so than ever; there are no one-size-fits-all silver bullets.
In this workshop attendees will use C#, SpecFlow and NUnit to code a real-world example, demonstrating one way of achieving success. We will also address common pitfalls and anti-patterns that you should try to avoid.
- Make the concepts of Specification by Example more tangible
- Jump start introduction to automating specifications through coding a real-world example
- Understand some of the challenges, particularly in a static language environment
Developers with experience writing software that targets the Microsoft .NET platform. Testers also welcome, but the focus will be more on the ‘executable’ part.
- A laptop with Windows and Visual Studio 2010/12, with SpecFlow preinstalled. If you don’t have a laptop you will be able to pair with someone else who does.
- Basic experience of TDD