In the case a developer has not constructed a controller, the setup
method of ActionController::TestCase will attempt to construct a
controller object.  If it cannot construct a controller object, it
silently fails.

I added a warning in this case, and I'd like to eventually deprecate the
behavior.  I can't think of why anyone would want to use
ActionController::TestCase and *not* test a controller.  Does anyone
know a reason *why* we would do this?

  
https://github.com/rails/rails/blob/master/actionpack/lib/action_controller/test_case.rb#L534-542

-- 
Aaron Patterson
http://tenderlovemaking.com/

Attachment: pgpgcDpDCUzhs.pgp
Description: PGP signature

Reply via email to