It took a while, but now I an totally convinced that controller specs should not access the database and stub as much as possible. I'm committed to that style of writing, yet from time to time I incidentally allow it to happen.
Is there a way to err on the safe side and have RSpec throw an error every time a controller spec attempts to access the database? And does it sound like a good idea? Thanks, Stefan
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
