Let me share my experience. On my side we do produce 3 documents before starting with rspec.
1- A web designer creates a design for a screen in conjunction with the marketing team and the analyst assigned to the this feature. The marketing dep, acts as the customer. 2-The analyst produce a "word" document containing the stories and scenarios attached to this screen. This work is done again in conjunction with the web designer cause she is also an ergonomist and the Marketing dep. The analyst has to have the approval of these stories-scenarios before he can share this info to the ruby programmers. 3- The analyst produce also a little spreadsheet defining all labels, fields and any specifities of the screen to eleminates any "second guess" of the ruby dev. As soon the ruby dep got those docs they start creating specs for this. For now we are not using cucumber yet. It is already a huge challenge for me to convience legacy programmers to learn ruby, rails OOP in the BDD way. In short term I plan to experience it. For now we are not having any tool to transfer stories-scenarios from our word doc to rspec file. If any of you have something for that, let me know. Rémi Gagnon On Tue, Mar 3, 2009 at 8:51 PM, Rich Morin <r...@cfcl.com> wrote: > At 16:41 -0800 3/3/09, Pat Maddox wrote: > > Not quite. Some customers don't want to sit down next to you as you > > write the stories. In that situation, we'll talk about features, I > > take notes, then I write up the features and ship them via email or > > wiki. They're still involved in the creation of stories and > > acceptance criteria, they're just not present when those criteria get > > entered into cucumber features. > > In the Ontiki project, I am acting as my own initial customer and the > primary customers (for at least a while) will be Ruby programmers. So, > I'm playing with the use of a pre-processor which allows use of eRuby > (for selection, repetition, and variable substitution), line folding, > etc. This DRYs out my editable files (fe/*.fe), while generating > readable and Gherkin-compliant feature (*.feature) files. > > This would not work well for a highly interactive situation, but it > might work in a situation like the one you describe. It may also give > us some useful feedback about useful extensions for Gherkin. > > -r > -- > http://www.cfcl.com/rdm Rich Morin > http://www.cfcl.com/rdm/resume r...@cfcl.com > http://www.cfcl.com/rdm/weblog +1 650-873-7841 > > Technical editing and writing, programming, and web development > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
