Hi Michael,
Wikipedia page on Spec by Example is pretty good (
http://en.wikipedia.org/wiki/Specification_by_example) and the Key Ideas page from Specificationbyexample.com (
http://specificationbyexample.com/key_ideas.html) is also a good introduction to the topic.
Communication is more important than automation - automation is not necessary, but it brings a set of benefits. See this post and related comments on the topic:
http://gojko.net/2010/03/01/are-tools-necessary-for-acceptance-testing-or-are-they-just-evil/ The mentoring programme is designed for people already practicing this that want to go beyond the basics. If you're looking for more basic stuff,
come to my workshop in June to learn about it:
http://sbelondon.eventbrite.com/ - there is a still active promo code "atuk" for members of this list to get £200 discount before 1st June.
gojko
On Monday, May 21, 2012 10:21:23 AM UTC+1, MHFJones wrote:
Hi Gojko,
For the benefit of those who might not know, what's specification by example?
From what I've read so far, is it including consistent examples throughout the development lifecycle, all the way through from requirements gathering to coding (and postlaunch testing) - examples being anything from mockups/screenshots to tables showing the correct output for each possible input (including edge cases etc)? Is running automated tests against those examples using a tool such as Cucumber or Fitnesse a necessary part of a full implementation of specification by example? (and something you'll discuss at the workshop)
Thanks,
Michael