raise an error when attempting to use allow(...).to have_received
tweak ws
[skip ci]
changelog for #788
[skip ci]
Merge pull request #788 from rspec/error_for_allow_have_received

raise an error when attempting to use allow(...).to have_received
Explicitly call out args passed into any_instance stubs.
Merge pull request #789 from dblock/explicitly-list-args

Explicitly call out args passed into any_instance stubs.
Updated travis build scripts (from rspec-dev)
Merge pull request #791 from rspec/update-travis-build-scripts-2014-09-26-for-master

Updates from rspec-dev (2014-09-26)
Forwardport 3.1.2 release notes.
Reorganize verified double specs.

The single `verifying_double_spec.rb` has gotten unwieldy and hard
to work with because it's so large. It's easier to work with smaller
spec files.

- Extract doubled class definitions into a support file.
- Move the method visibility specs into their own file.
- Move class/object/instance double specs into their own files.
- Move general verifying double construction specs into a separate file.
Make doc strings a bit more accurate.
Rewrite verifying message expectation specs.

- Move them under `verified_doubles` sub directory.
- Use more of an integration style rather than a mock-based
  unit style.
- This is easier to work with; the other specs surprised
  me in that I had to explicitly expect the error generator
  not to receive a message in order to write a spec for the
  "allowed" case (since it was `as_null_object` it would not
  fail automatically). This surprised me when trying to add
  some new specs here.
- This also fixes the spec for the `any_args` case. The old spec
  did not fail when I temporarily removed the special `any_args`
  handling, because the expected method for that example accepts
  1 argument, and without the `any_args` special handling, it would
  naturally be treated as a single argument.
Merge pull request #792 from rspec/reorganize-verifying-double-specs

Reorganize verifying double specs
Improve wording of docstring.
Correct error with have_received counts
* add triangulation example for have_received error
* rescue RSpec::Mocks::MockExpectationError when replaying expectations,
  we need to count them all.
Don't raise an expectation when counting in have_received
extend rubocop class definition
changelog for #793
[skip ci]
Merge pull request #793 from rspec/fix_issue_with_have_received_matcher

Wrong error message generated by have_received matcher when method was called 2 or more times than expected
fixup changelog after #793
[skip ci]