On Mon, Jul 20, 2009 at 11:05 PM, Chris Sund<ch...@silhouettesolutions.net> wrote: > > I am finally to the point in the rspec book where it describes how to > implement controller specs, so I thought what the heck, I'll give it a > try.
Heh. Points to you for ambition! You might not have realized this (because the RSpec book makes it sound like it should *all* be easy) but starting with a Rails controller spec for your very first spec is a bit like saying "I was thinking of getting scuba certified... Ooooh, CAVE DIVING! Let's start with that first!"* On the upside, if you start there and really get to *understand* what's going on, you should be relieved when most of the rest of it is pretty smooth sailing. There are very few common Ruby idioms that have such tight coupling as Rails controllers, so very few tasks are so hard to spec in isolation. You'll almost never have to mock anything else as ferociously. Model specs in particular will feel like sunshine and puppies. So go you! -- Have Fun, *(Granted, I don't think anyone has ever kicked up silt while writing a controller spec, lost hold of their guide line, gotten hopelessly lost, and died many hours later in the cold and dark. Yet. That only happens to J2EE programmers.) Steve Eley (sfe...@gmail.com) ESCAPE POD - The Science Fiction Podcast Magazine http://www.escapepod.org _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
