Please log in to watch this conference skillscast.
When creating our scenarios, we want to fully describe the desired functionality, but not over-describe it. We want our scenarios to do more than check for correct operation. We want to paint a picture of what’s intended that aids understanding by others (or even ourselves) in the future.
Which details should we leave visible, and which should we hide? We’ll look at ways to distill our scenarios down to their essence, and remove distracting incidental details.
YOU MAY ALSO LIKE:
- Got The Perfect Agile Model? Here’s What You Should Know About Agnostic Agile (in London on 25th July 2017)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 1st - 3rd November 2017)
- Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)
- Serverless Architecture with Azure Functions with Christos Matskas! (in London on 29th November 2017)
Distilling the Essence
George is a software development consultant and coach with over thirty years of experience creating software ranging from small embedded systems to corporate enterprise systems.