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 27th - 29th March 2019)
- Uncle Bob Martin's Clean Code Workshop on Agile Software Craftsmanship (in London on 11th - 12th April 2019)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 30th September - 2nd October 2019)
- P3X - People, Product & Process eXchange 2019 (in London on 31st October - 1st November 2019)
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.