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
You could use something like NullDb to achieve this, I think:
http://www.slideshare.net/bmabey/disconnecting-the-database-with-activerecord
On 3 Mar 2010, at 20:43, Stefan Kanev wrote:
It took a while, but now I an totally convinced that controller
specs should not access the database and
