On Mar 4, 2008, at 7:43 AM, Chris Parsons wrote: > [snip details about story & spec workflow] > > Sound like a lot of work, but given practice you can zip through these > steps very quickly. You also get a free 'focusing tool' (lose sight of > where you are? just run the story test and write more specs). > > Hope this is helpful. Maybe I should write up an extended example as a > blog post, including mocking etc, as it seems to come up a lot. > > Thanks > Chris
Sorry to resurrect an old thread... I've just spent the last 10 hours working on understanding user stories and their role in designing code. Here's what I've done: * watched the "RSpec User Stories" peepcode * scoured this newsgroup for tips & suggestions * used Chris' methodology to BDD a new app So far things are going well though the process is S L O W. I've tried to cobble together tips from other threads regarding directory structure for the stories, steps & specs amongst other things, but it just feels really scattered to me. I would love to see Chris put together a more detailed example of his workflow. It's likely I am making some boneheaded mistakes that I just can't pick out yet. When I'm further with my example project, I'll try to post it up somewhere (or turn it into doc for the rspec site) so others can learn from my mistakes. cr _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
