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:
- Jenny Martin and Pete Buckney's BDD From Start to Finish - Successful Delivery through Continuous Collaboration (in London on 26th - 28th February 2018)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 19th - 20th March 2018)
- The Conference formerly known as Agile Testing & BDD eXchange 2018 (in London on 8th - 9th November 2018)
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.