Hey guys, I’m trying to work out the order of development for features
in an app. I’m struggling with using stories to drive development.
So when looking at things, it seems to me to be the best idea to first
write stories, then view specs, then controller specs, then model
specs…but how to actually do it is what confuses me. Anyone know of
any screencasts or tutorials working through the development of a
feature in this way?
Nathan S.
[email protected]
rspec 1.1.3
rspec_on_rails 1.1.3
rails 2.0.2
Nathan S. wrote:
[email protected]
rspec 1.1.3
rspec_on_rails 1.1.3
rails 2.0.2
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
There is a new peepcode on story runner… I have yet to watch it fully
but if it is like the other peepcode rspec screencasts it will be an
excellent source.
Also, check out Pat Madox’s screencast about the story runner. It is a
little dated but it is still good:
There are also some posts that cover the basics of plain text stories…
Here is a more recent one with some other links at the bottom:
http://www.tomtenthij.co.uk/2008/1/25/rspec-plain-text-story-runner-on-a-fresh-rails-app
I also just posted one about using webrat to help write stories (webrat
absolutely rocks!):
http://www.benmabey.com/2008/02/04/rspec-plain-text-stories-webrat-chunky-bacon/
The screencasts go over the development process while the posts are more
of how-tos for story runner.
-Ben
On Feb 3, 2008 9:19 PM, Nathan S. [email protected] wrote:
Hey guys, I’m trying to work out the order of development for features
in an app. I’m struggling with using stories to drive development.
So when looking at things, it seems to me to be the best idea to first
write stories, then view specs, then controller specs, then model
specs…but how to actually do it is what confuses me. Anyone know of
any screencasts or tutorials working through the development of a
feature in this way?
hrm…yeah it’s a little tough. I think we’re all still figuring it
out a bit and there’s not a lot of solid info. I personally feel that
my understanding has developed a bunch since I made my last Story
Runner screencast, so maybe I’ll try to put one out another one next
weekend.
Here’s what I do, in a nutshell:
Write out a story, without implementing any of the step runners
Write the step runner implementations to get an idea of what stuff
I’ll need to make it run
Delete those step implementations - that was just to get the blood
flowing
Write the first step implementation
Drop out of the story and start writing specs for the behavior I need
to pass the story step
When that step is passing, I head back to the story and work on the next
step
Rinse, repeat
???
profit!
Hope that’s enough to get you started, in addition to the good links
that Ben posted. And like I said, I’d like to do a new screencast
this weekend.
Pat
sounds good guys, thanks 
Nathan S.
[email protected]
rspec 1.1.3
rspec_on_rails 1.1.3
rails 2.0.2