Re: [scrumdevelopment] Requiring "Cucumber" (Gerkin) in Stories
I essentially agree with other posters and don't like a one-size-fits-all approach to expressing story tests.
In particular, the Gherkin style can get very wordy, put too much emphasis on prose, and is a pain when there are a bunch of permutations of very similar scenarios.
I recently gave a presentation at a couple of conferences where I presented 8 patterns for expressing story tests, as well as context for when each pattern might be more appropriate. I also give concrete examples. You can download the preso PDF here:
From: Adam Sroka <adam.sroka@...>
Sent: Monday, August 20, 2012 7:31 PM
Subject: Re: [scrumdevelopment] Requiring "Cucumber" (Gerkin) in Stories
IMO, this has the same sort of problems the old "as a... i want to... so that..." format that have been discussed at length on this list. There are going to be things you want to say that are best said another way. There are also going to be things that don't make any sense as stories but that can be easily massaged into this format. Following the rules in either case will increase the likelihood that you miss something.In general, when you overly formalize human language it bites you back. Just read any legal document written, oh... ever. I think that's why things like big visible charts, conversations, cards, games, etc. are so effective. They bring us back to basic forms of human communication in which we can actually be fluent and get our points made.
On Mon, Aug 20, 2012 at 6:20 PM, Pito Salas <pitosalas@...> wrote:This might be an old question so feel free to point me to the relevant link…What are your opinions about standardizing on writing all scrum stories in "Gerkin" or "Cucumber" format? I am interested to hear about best practices, and any comments folks have from their own experiences.Thanks,Pito-------Check out http://www.salas.com and http://www.blogbridge.com/look