[rspec-users] Troubles with route_for

Randy Harmon r_j_h_box-sf at yahoo.com
Tue Jan 12 02:06:04 EST 2010


On 1/11/10 9:22 PM, Nick Hoffman wrote:
> David Chelimsky wrote:
>   
>> I'd recommend using the route_to matcher that was added in 1.2.9 
>> instead.
>>
>> http://codepad.org/fLcxyA9N
>> http://rspec.rubyforge.org/rspec-rails/1.2.9/classes/Spec/Rails/Matchers.html#M000029
>>
>> It's more reliable, and aligns better with the rspec matchers API.
>>
>> Cheers,
>> David
>>     
> Thanks for that, David. I updated my spec (http://codepad.org/F828X7Fg). 
> For some reason though, it's still failing: http://codepad.org/s65Ckubc
>
> Just in case, this is what I have in routes.rb: 
> http://codepad.org/rJfIhbM6
>
> There must be some tiny detail that I'm missing here...
>   
Yes, there must.  I think you've tried to twice define the route, and
the test shows you which one actually is being used.  I'll suggest
commenting out one of those routes at a time, and see whether the new
test results are illuminating. 

Randy



More information about the rspec-users mailing list