"RESTful" controller specs in rails

Testing RSpec
1

So, what’s the awesome sauce everyone is using for this? In the past
I’ve used shared behaviors, and rspec_on_rails_on_crack to solve all
the repetition in the controller specs, but I’ve been away from rspec
for a while, and the controller specs in the rails project I’m working
on are a mess. So… what’s the best/recommended approach these days?

Cheers,
-foca

2

I use resource_controller, and then don’t need to write controller specs
because it’s all boiler-plate. If I add any custom behavior that needs
more focused testing than cucumber provides, I can just write a couple
specs to cover it.

Pat

3

On 4 Jan 2010, at 22:46, Pat M. wrote:

I use resource_controller, and then don’t need to write controller specs because it’s all boiler-plate. If I add any custom behavior that needs more focused testing than cucumber provides, I can just write a couple specs to cover it.

Ditto: I use resources_controller (note different name!), which already
has comprehensive tests, and only write specs for any non-boilerplate
behaviour which I add.

Cheers,
-Tom