Plaint-text stories should include list of step files required
Reported by Craig Buchek | July 25th, 2008 @ 05:20 AM | in No-Milestone-Assigned
All the Ruby files used to run my plain-text stories are almost exactly the same, except for the story's filename and the steps to run.
I think it would be a better idea to do away with the Ruby files altogether, and have stories/all.rb (or some other file) get the info from the story files themselves. All we'd have to do is add a line like this to each story:
Uses steps: login, webrat, navigation, database
If this is something that you'd be interested in, I would be willing to code up an initial implementation.
Comments and changes to this ticket
-
Eric Stewart July 25th, 2008 @ 06:17 PM
I'm headed the same direction as you are on this. We have eliminated the individual story.rb files and replaced with a yaml file per story containing this information (story metadata) that gets read in by a common runner script. I'd love to have only the story file at the end of the day, but am not crazy about adding clutter to the plaintext story file.
Also, we are finding this story specific yaml file useful for other metadata regarding the story besides the steps to use (e.g. sources for data to use during story execution, settings for story setup/teardown done via listeners, etc). We are using stories for a combination of acceptance testing and integration testing across an array of different application though, which may be a bit more complex than the average user of rspec stories.
I'm still thinking about better ways to do all this, however, and am interested in seeing what others think about approaching this problem. It has been quite easy to build what we are doing around rspec, but might be nice to have a common way to solve the problem if others are having it too.
-
Joseph Wilk August 1st, 2008 @ 11:10 PM
Have you checked out
aslakhellesoy's cucumber - http://github.com/aslakhellesoy/.... Sounds like it might do what you mentioned.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Behaviour Driven Development for Ruby.
