I have not found this approach to work well. What we did find to work well was:
- BA to write story, acceptance criteria, and possible draft of the cukes - Cukes to be revised by a QA / BA pair, or programmer / BA pair depending on your team You do not want to say "we have these steps, go write a feature". You want to write a feature, and then create and adapt the steps and the feature. The programmer / QA will know what steps are available and what specific steps can be modified to be made more generic, or whether a new step needs to be created. Also, if you find yourself using the raw webrat steps or specifying CSS/XPath search paths in your features, you are "Doing It Wrong". On Thu, Oct 13, 2011 at 10:36 AM, Dmytrii Nagirniak <[email protected]>wrote: > Hi, > > I want to allow our Business Analyst guy to be able to write the Cucumber > specs. > > The things that worry me are: > > - list of all step definitions (he needs to know those or otherwise every > line of the feature will need to have a step def) > - the speed of running specs (if it'll take 20 mins, I just won't run > those) locally > - how far can you go about it with relatively JS heavy app > > Any experience, suggestions etc? > > Or is Cucumber really for eating? :) > > Cheers, > Dima > http://www.ApproachE.com > > > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- Michael Pearson The Bon Scotts; http://www.thebonscotts.com -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
