Derek Prior 1dacfbabf3 Fix incorrect assert_redirected_to failure message ... In some instances, `assert_redirected_to` assertion was returning an incorrect and misleading failure message when the assertion failed. This was due to a disconnect in how the assertion computes the redirect string for the failure message and how `redirect_to` computes the string that is actually used for redirection. I made the `_compute_redirect_to_loaction` method used by `redirect_to` public and call that from the method `assert_redirect_to` uses to calculate the URL. The reveals a new test failure due to the regex used by `_compute_redirect_to_location` allow `_` in the URL scheme.		2013-09-19 09:23:20 -04:00
..
abstract	Move abstract's controller tests to AV	2013-08-25 11:40:11 +02:00
assertions
controller	Fix incorrect assert_redirected_to failure message	2013-09-19 09:23:20 -04:00
dispatch	Merge pull request #11912 from jonkessler/respond-to-signature-fixes	2013-08-31 14:41:14 -07:00
fixtures	Remove helper fixtures not used in any test	2013-09-09 14:19:09 -07:00
journey	Skip Rack applications and redirects when generating urls	2013-07-16 13:39:17 +01:00
lib/controller	Remove unused fixtures and models from AP tests	2013-08-25 11:39:14 +02:00
routing	Fix failing test missed for the past year :(	2013-07-17 08:56:34 +01:00
tmp
abstract_unit.rb	Remove RenderERBUtils from AP (only AV use it)	2013-08-25 11:39:10 +02:00