Without that patch when using ActiveModel::AttributeMethods
in a class that does not respond to `attributes` method,
stack level too deep error will be raised on non existing
method. While documentation is clear that you need to define
`attributes` method in order to use AttributeMethods module,
`stack level too deep` is rather obscure and hard to debug,
therefore we should try to not break `method_missing` if
someone forgets about defining `attributes`.

The commit 2f632f53 extracted the
options into constants and while doing so, there was a minor error of
using a wrong constant name.

changelog entry for deprecated ActionController::Integration, ActionCont...

Don't hardcode assets route skipped in route inspector

Bump Sprockets to 2.2.0 in master

Refactored watchable_args and build_original_fullpath methods in Rails::Application

Generated attributes refactor

changelog entry for deprecated ActionController::Integration, ActionController::IntegrationTest, ActionController::PerformanceTest,ActionController::AbstractRequest, ActionController::Request, ActionController::AbstractResponse others

deprecated action_controller integration test and performance test

Deprecate ActionController::Integration, ActionController::IntegrationTest, ActionController::PerformanceTest,ActionController::AbstractRequest, ActionController::Request, ActionController::AbstractResponse, ActionController::Response and ActionController::Routing

refactor response_body= method

response_to?(:each) returns false for strings in ruby 1.9, so there is no need for these checks