[rspec-devel] Game of Life questions
Ian Dees
undees at gmail.com
Tue Aug 28 14:56:35 EDT 2007
What a coincidence! It was this very morning that I took the plunge
and switched from my stock 1.0.8 install to a gem built from Dan's
branch, and I had some of the exact same questions.
> > > > 1) It was hard to figure out how to run the game of life example.
> > > > First I looked for a Rake task and found none. Then I looked for
> > > > instructions in a README and found none.
I stumbled here, too, trying to figure out how to run my own story
file. I spent a little while playing with spec's -U option and
StoryRunner before realizing that the right way is just to use plain
ol' ruby and require 'spec/story' in my story file.
> > > This is all stuff we need to do, but keep in mind this is not a release yet.
Want me to take a first stab at a really short README for the RBehave
examples? (Finally, something I might be semi-qualified to do for the
story effort! ;-)
> > > Agree. Given the discussions we've been having recently about bridging
> > > the RSpec/Test::Unit gap, we should have a single command that can
> > > field stories, specs and tests.
As a RSpec user, I'd say either a "bin/spec" that runs stories without
needing too many flags/options, or a separate "bin/story" would feel
fine.
> > > project/behaviour/objects
> > > project/behaviour/stories
So if I understand correctly, "objects" is the catch-all for things
that aren't models, views, or controllers. What about for non-Rails
apps? When I have my GUI testing hat on, "stories" and "examples"
seem clearer than "stories" and "objects."
--Ian
More information about the rspec-devel
mailing list