
By Geoffrey Grosenbach. Technical consultation from RSpec committer David Chelimsky.
RSpec 1.1 introduces a new feature…user stories.
You can now write plain-text stories that fit into the XP style of development. You can use stories written by customers to execute code against your application, or you may choose to use stories as a part of your development workflow.
The implementation of RSpec stories also fills a gap once filled by Rails’ integration tests. RSpec stories run against the whole stack of your application, including routes, controllers, models, and views.
This 50-minute screencast introduces stories and shows you how to use them with pure Ruby code or inside a Rails application.



This screencast assumes a knowledge of the RSpec behavior driven development framework. See the PeepCode RSpec basics screencast for an introduction.
Revision 1 (Notes) · Created: Jan 10, 2008 · Length: 50 min · 62 MB
“They are top quality screencasts, straighforward material...I just saw the Rspec Stories one and I really enjoy it. I was already into BDD, but this really got me closer to be 100% BDD-man.” Lucas Florio, IT Solutions Developer
“PeepCode really helped me set the tone and level of abstraction of my tests -- crucial things to get right.” Ian Dees
“PeepCode is awesome!” Tim O'Reilly, O'Reilly Media
“These things are fantastic and the price is a steal. I strongly urge you to support this effort and buy the episodes. What a terrific way to learn!” Scott Barron, Rails Core Committer
“[The] git PeepCode book is awesome. Congrats on a job very well done. This should be required reading for all git users.” Jamis Buck, Rails Core Alumnus
“It was refreshing to read about git from the bottom up, and not compared to SVN. I was at the stage where I could do most of the basic tasks I used to do in SVN, but lacked a fundamental understanding of how it was working under the hood...Understanding all those concepts really helped me grok why the higher level commands and workflows work the way they do, and how to avoid some of the pitfalls.” James, in blog comment
“Even if you are not planning to write a Rails plugin, you should absolutely check this book, there are great insights about how Rails works and you will figure out that building a plugin is as easy as anything in Ruby, it’s just a matter of knowing where to place your code.” Codevader Blog
Login or signup and enter the code on your account page. If it is still valid you will be able to browse the list of products and redeem an episode.