[rspec-users] rspec-users Digest, Vol 20, Issue 6
voodoorai2000 at gmail.com
Mon Feb 4 12:00:50 EST 2008
On Feb 4, 2008, at 5:07 PM, rspec-users-request at rubyforge.org wrote:
> On 4.2.2008, at 14.54, Raimond Garcia wrote:
>> I'm trying to test the behavior of a route with a delete method.
>> Something like this:
>> When "the admin clicks on 'delete'" do
>> delete admin_blog_path(@blog)
>> which raises the following exception:
>> NoMethodError: You have a nil object when you didn't expect it!
>> The error occurred while evaluating nil.env
>> If I change the delete, for a get or a post it works like a charm.
>> What am I missing here?
> I would recommend against using the restful named routes in your
> stories. You want to test your full stack there, right, so just use
> the url. I also recommend using Webrat in conjunction with stories: http://www.benmabey.com/2008/02/04/rspec-plain-text-stories-webrat-chunky-bacon/
> That way you are much more testing the behaviour of the application
> rather than its implementation.
> If you only want to test that the route is working, it would imho
> belong to the controller specs, not to the stories.
> Jarkko Laine
The restful routes, seem clearer than using urls, maybe not so much
for this case, but for very long urls, that include for example the
title of a blog, I would rather use blog_path(@blog).
Yes, I want to test the full stack, for sure! However, I don't see how
using named routes, stops you from doing this....
Webrat two thumbs up, I've been using selenium up to now, but would
like to try other alternatives to see which one works better.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rspec-users