Well, they should think of cucumber, and as they get more used to the cukes as they pair with the devs they may end up being able to write their own cukes.
AFAIR, we ended up with BAs writing cukes, marking them as @wip and committing them to git for later use. On Thu, Oct 13, 2011 at 11:17 AM, Dmytrii Nagirniak <[email protected]>wrote: > > Cheers, > Dima > http://www.ApproachE.com > > > > > On 13/10/2011, at 11:01 AM, Michael Pearson wrote: > > 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. > > > Good point. > So you suggest letting the BA guys to write everything without thinking of > Cucumber. > Then just sit together and "translate" it? > > It might work pretty well. > > -- > 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.
