I just upgraded Rails from 0.12.1 to 0.13.1 and then updated my app by
selectively accepting the new files with ''rails .''. I think I
did
that process correctly. My problem is that now 15 of my functional
tests are failing. All failures are related to assert_redirected_to.
I have about 60 assert_redirected_to calls in my tests. So, not all
of them are failing.
I''ve got one failure like this:
<"/bogus/location"> is not the redirected location
<"http://localhost/bogus/location">
So Rails 0.13.1 prepends http://localhost to redirections now?
I''ve got a bunch of failures like this:
response is not a redirection to all of the options supplied
(redirection is <{:controller=>"/users",
:action=>"list"}>)
When my assertion is this:
assert_redirected_to :controller => "/users", :action =>
"list"
Finally, I''ve got a bunch of failures similar to this:
response is not a redirection to all of the options supplied
(redirection is <{:controller=>"/match_profiles",
"user_id"=>6,
:action=>"new"}>)
When my assertion is this:
assert_redirected_to :controller => "/match_profiles", :action
=> ''new''
So now the assertions are testing the redirected parameters too?
I''m a little disappointed I didn''t have any warning this was
going to
break. Was this planned? I carefully studied the release notes and
what other information I could find. I waited to upgrade to see what
issues came about. I''m really surprised I didn''t have any
warning
about this.
Are these bugs in Rails? Do I fix my tests only to have to fix them
again later? I did some searching of the trac database and found this
issue. Are they related?
http://dev.rubyonrails.com/ticket/1472
--
doug-jGAhs73c5XxeoWH0uzbU5w@public.gmane.org