[ci skip]

This reverts commit 09793f88.

* We ended up breaking specs that relied on non-anonymous routes. We
  will investigate a better solution for 2.13 instead.

* Requires Bundler 1.3.0.pre
* Has its own `bin/` directory

* This will require bumping this version periodically, but leaving the
  version has caused hanging of the `bundle` command for some folks

* To support redirection and generation of URLs from other contexts
* Fixes #573

* Fixes #654

This reverts commit 3b28ce7a.

* OperatorRegistry now matches on ancestor chain, so this change is no
  longer necessary. See
  https://github.com/rspec/rspec-expectations/commit/e5e5a7475cf1f993b9e1bac8df485df29a544d95.

[ci skip]

* This allows Rails assertions to use minitest assertion methods like
  `assert_equal` and `message` without interfering with RSpec example
  groups. Especially in the case of something like `message`, it's
  plausible that a user would setup a `let(:message)` and we would not
  want it to conflict with Rails attempting to use the `message` method
  from minitest.

* The use of class variables is unfortunate, but it's the only way I
  could think of (right now) to avoid using `define_method` and paying
  the price of a closure for every method call to the isolated class.

* Fixes #635

* ... where valid? does not take an argument
* Closes #648

For example spec/apifoobar should not have the RequestExampleGroup included
but spec/api should.
Documents also the two additional paths for integration tests, spec/integration and
spec/api.

'rspec' is not longer installed:
https://github.com/rspec/rspec-rails/commit/f5a573518420629b80f10bf1b8a01faf54ae1e1d

Like ActiveRecord, it is optional and its railtie may not
have been required.

* Rails 4 deprecates #scoped in favor of #all

[ci skip]

This fixes various issues with the integration between RSpec and Capybara 2.0.

- It includes Route helpers, these were previously unavailable, due to
  the fact that the only reason they are available in request spec is
  that those delegate via method_missing to an IntegrationTest instance.

- It adds the `:feature` type to all features. This way people can
  include module into `:type => :feature` examples and they will work
  when their specs are places in this folder.

David previously commented that he didn't want to add Capybara specific
behaviour outside of `rspec/rails/capybara`. I was careful to avoid
doing that. The feature example group does not explicitly include
Capybara, instead, Capybara is included due to Capybara itself hooking
into `:type => :feature`. This is much cleaner than the way it was
before.

I tested this against both a freshly generated Rails app, as well as an
existing, rather large project, both worked well.

This reverts commit 96e1c334.

* We'll instead use an implementation that adds a proper
  FeatureExampleGroup (see #632)

Really rspec-2.11.1 or rspec-rails-2.11.1

Fixed confusing type error.

Capybara feature specs may use Rails URL helpers