As reported in #348, model#valid? is called with one argument while ActiveResource::Validations only defines #valid? without an optional argument. The interface of ActiveResouce::Validations#valid? is the same for A'resource in Rails 3.2 and the one extracted into a gem. Rails 3.2 version: https://github.com/rails/rails/blob/3-2-stable/activeresource/lib/active_resource/validations.rb#L123 Gem version: https://github.com/rails/activeresource/blob/master/lib/active_resource/validations.rb#L160
The rails assertion that underlies the `route_matcher` matcher has changed in Rails 4 to depend on the `message` method from MiniTest. RSpec is smart enough to make that method available, but only for controller and routing specs (and only in 2.13.1+). I marked the `route_matcher` specs as controller specs and updated the rspec-rails gem development dependency to 2.13.1 or later (but less than 3).
Rails 4 includes strong parameters and removed attr_accessible (protected attributes). I removed the strong_parameters development dependency and added it to all non-4.0 appraisals. I also added the 'protected_attributes' gem to the 4.0 appraisal because the test suite examples make heavy use of attr_accessible.
* Add Ruby 2.0 support to the Appraisals * Update travis to test 2.0.0 with the 3.2 gemfile. Clean up the travis matrix to favor the include syntax over exclude. * Edit gemfile.locks to point to relative paths.
* See issue #252 * Also changes bourne dependency into a development dependency
> Use a pessimistic version in the Gemfile for gems that follow semantic > versioning, such as rspec, factory_girl, and capybara. https://github.com/thoughtbot/guides/tree/master/best-practices * Upgrade dependencies so specs run on new Bourne. * Use semantic versions in step_definitions gems. * Rely on ActiveSupport::Dependencies.clear for reloading constants. http://rkh.im/code-reloading
* fixes #108 : RSpec 2.10 compatibility * remove unnecessary attr_readr