My workflow is the following: Stories->Spec Views->Spec Controllers-Spec Models
I'll write a few stories of what I think should it happen. Then I'll write my specs of what should show (and also do some static html page mockups) Then I'll spec my controllers and models I'll go back to my stories to see if they need adjusting because my perceptive of how the app changed Then I run my stories and make them pass. Then I write a few stories and repeat. I constantly step move back and forth. I think Stories and BDD greatly assists you to shape your idea. Write stories for what you can think of and then move on to specing. You don't need complete stories you can also go back and fill them in later. On Feb 18, 2008 2:57 AM, Victor Asteinza <[EMAIL PROTECTED]> wrote: > I am new to BDD and have been doing some reading and playing with > rSpec. I am a little confused. I am not sure what the best practice > for using stories and specs. Should I be writing stories first, then > specs that would fulfill those stories, and then write the > implementation code to have everything pass? At first that seems a > little redundant. > > I understand that the stories let you write the behavior in plane > English, which I can see it being useful when dealing with non > technical users. But if I am developing an internal app I am > struggling with whether I should develop the stories first and then > move on to the specs. > > Opinions? Experiences? > > Thanks, > Victor > _______________________________________________ > 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
