rspec-mocks 2.99.4 → 3.0.0.beta1

checksums.yaml

@@ -1,7 +1,15 @@
 ---
-SHA1:
-  metadata.gz: 471207f568702e87294befee6dcfc4516e1fa21f
-  data.tar.gz: a6049d633e700b93394acdd366bf7b563224d312
-SHA512:
-  metadata.gz: a2c42ecb51e479ba57358c837a3a7d5befe5e3880ac6ece6b948b7f5a6955f2473b745cb19e4cbe0b2e31d8bd2a8f3b01ce9e9aaa95004d2b861fb780f704f10
-  data.tar.gz: 214851eb67b0ac4a03bf1db3433c1ee94d13130eed03f583f834d32183a15d99313c478c2178c683345e60d24bb2fa54a68abf0387e6c498856b3b309b6fb64e
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    MWQyODY3ZjBkNmUxYWY1ZjFlZWNlM2Q0NjZlY2M1OTEwOTI3N2E1ZQ==
+  data.tar.gz: !binary |-
+    YzI0OGE3YzFmZDQ4MTc5ZmJlODExYjNjNDE5MzMyOGI4ZTE2ZDY2MQ==
+!binary "U0hBNTEy":
+  metadata.gz: !binary |-
+    OTA4ZmE4NjJhNDhjYTFmMWU4MmM3OTkzMTk3OTQ3M2YyYTNmMzljYzQzNDFm
+    MjgwMzE0NDlmZDFmYzVkMzIwZWIzOGYxNjZlN2U1MDMwZDIwNGYxZDkzYWFj
+    MDAzM2NmMWEyNDA1NTg5OTBmMzViMzdhYjRlMTUyODNmMDJkMjU=
+  data.tar.gz: !binary |-
+    YjExYjNmYzZhMTAyZjQyN2RjNWY1NmNhMjRiNmU5NDhjOTY0NWNiYzMxOWUy
+    MGMzOGIzOTYzNDhmOWNlNzVkODQ5ZmYyN2RmN2MwZGM2ZThmMWIwY2U3NGIx
+    M2Q3ZTFhNTVkZjFjZmJhNmQ4M2NkNTJhMGRiN2IzMmY3ZThkNGQ=

checksums.yaml.gz.sig

@@ -0,0 +1,2 @@
+}��{ �ͨ�k}���{Z�E	����@;P�?�t���.�+��D.�d����
�p3x|�Vv��hhv�p@�i�R8���E(���¸D~�����~�3�jC1Of+Wm7*��k�
+�3�

data.tar.gz.sig

@@ -0,0 +1 @@
+�旺]v�����h��(*�z(��������:�d-XH�?ibI�4L��0*�ʆ˫K��Y?D��u<��);�p��]8�ҥ��P��8�ۥ��v<�MZ�M@���3��ӑ۶�Y���Ͷ�D�ОP	�Mɭ�(B�[�Vk�"8��)'�Hs�%�j�ldyg�����Ԅ�f��đ��)�ѻ�gb�L��K��;7r)գC�1��	�lN�vKϣ!���Qr$9�P�ZI� u�'�a��=[�6/e

data/Changelog.md

@@ -1,70 +1,71 @@
-### 2.99.4 / 2015-06-19
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.3...v2.99.4)
-
-Bug Fixes:
-
-* Add missing deprecation for using `with` with no arguments e.g. `with()`. (Yousuke, #970)
-
-### 2.99.3 / 2015-01-09
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.2...v2.99.3)
-
-Bug Fixes:
-
-* Fix regression that caused an error when a test double was deserialized from YAML. (Yuji Nakayama, #777)
-
-### 2.99.2 / 2014-07-21
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.1...v2.99.2)
+### 3.0.0.beta1 / 2013-11-07
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.0.beta1...v3.0.0.beta1)
+
+Breaking Changes for 3.0.0:
+
+* Raise an explicit error if `should_not_receive(...).and_return` is used. (Sam
+  Phippen)
+* Remove 1.8.6 workarounds. (Jon Rowe)
+* Remove `stub!` and `unstub!`. (Sam Phippen)
+* Remove `mock(name, methods)` and `stub(name, methods)`, leaving
+  `double(name, methods)` for creating test doubles. (Sam Phippen, Michi Huber)
+* Remove `any_number_of_times` since `should_receive(:msg).any_number_of_times`
+  is really a stub in a mock's clothing. (Sam Phippen)
+* Remove support for re-using the same null-object test double in multiple
+  examples.  Test doubles are designed to only live for one example.
+  (Myron Marston)
+* Make `at_least(0)` raise an error. (Sam Phippen)
+* Remove support for `require 'spec/mocks'` which had been kept
+  in place for backwards compatibility with RSpec 1. (Myron Marston)
+* Blocks provided to `with` are always used as implementation. (Xavier Shay)
+* The config option (added in 2.99) to yield the receiver to
+  `any_instance` implementation blocks now defaults to "on". (Sam Phippen)
 
 Enhancements:
 
-* Warn about upcoming change to `#===` matching and `DateTime#===` behaviour.
-  (Jon Rowe, #735)
-
-### 2.99.1 / 2014-06-12
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.0...v2.99.1)
-
-Bug Fixes:
-
-* Fix bug that caused errors at the end of each example
-  when a `double.as_null_object` had been frozen. (Yuji Nakayama, #698)
+* Allow the `have_received` matcher to use a block to set further expectations
+  on arguments. (Tim Cowlishaw)
+* Provide `instance_double` and `class_double` to create verifying doubles,
+  ported from `rspec-fire`. (Xavier Shay)
+* `as_null_object` on a verifying double only responds to defined methods.
+  (Xavier Shay)
+* Provide `object_double` to create verified doubles of specific object
+  instances. (Xavier Shay)
+* Provide 'verify_partial_doubles` configuration that provides `object_double`
+  like verification behaviour on partial mocks. (Xavier Shay)
+* Improved performance of double creation, particularly those with many
+  attributes. (Xavier Shay)
+* Default value of `transfer_nested_constants` option for constant stubbing can
+  be configured. (Xavier Shay)
+* Messages can be allowed or expected on in bulk via
+  `receive_messages(:message => :value)`. (Jon Rowe)
+* `allow(Klass.any_instance)` and `expect(Klass.any_instance)` now print a
+  warning. This is usually a mistake, and users usually want
+  `allow_any_instance_of` or `expect_any_instance_of` instead. (Sam Phippen)
+* `instance_double` and `class_double` raise `ArgumentError` if the underlying
+  module is loaded and the arity of the method being invoked does not match the
+  arity of the method as it is actually implemented. (Andy Lindeman)
+* Spies can now check their invocation ordering is correct. (Jon Rowe)
 
 Deprecations:
 
-* Deprecate freezing a test double. (Yuji Nakayama, #698)
+* Using the old `:should` syntax without explicitly configuring it
+  is disabled. It will continue to work but will emit a deprecation
+  warning in RSpec 3 if you do not explicitly enable it. (Sam Phippen)
 
-### 2.99.0 / 2014-06-01
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.0.rc1...v2.99.0)
-
-No changes. Just taking it out of pre-release.
-
-### 2.99.0.rc1 / 2014-05-18
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.0.beta2...v2.99.0.rc1)
-
-Deprecations:
-
-* Deprecate `RSpec::Mocks::TestDouble.extend_onto`. (Myron Marston)
-* Deprecate `RSpec::Mocks::ConstantStubber`. (Jon Rowe)
-* Deprecate `Marshal.dump` monkey-patch without opt-in. (Xavier Shay)
-
-### 2.99.0.beta2 / 2014-02-17
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.99.0.beta1...v2.99.0.beta2)
-
-Deprecations:
+Bug Fixes:
 
-* Deprecate `RSpec::Mocks::Mock` in favor of `RSpec::Mocks::Double`.
-  (Myron Marston)
-* Deprecate the `host` argument of `RSpec::Mocks.setup`. Instead
-  `RSpec::Mocks::ExampleMethods` should be included directly in the scope where
-  RSpec's mocking capabilities are used. (Sam Phippen)
-* Deprecate using any of rspec-mocks' features outside the per-test
-  lifecycle (e.g. from a `before(:all)` hook). (Myron Marston)
-* Deprecate re-using a test double in another example. (Myron Marston)
-* Deprecate `and_return { value }` and `and_return` without arguments. (Yuji Nakayama)
+* Fix `and_call_original` to handle a complex edge case involving
+  singleton class ancestors. (Marc-André Lafortune, Myron Marston)
+* When generating an error message for unexpected arguments,
+  use `#inspect` rather than `#description` if `#description`
+  returns `nil` or `''` so that you still get a useful message.
+  (Nick DeLuca)
 
 ### 2.99.0.beta1 / 2013-11-07
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.4...v2.99.0.beta1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.4...v2.99.0.beta1)
 
-Deprecations:
+Deprecations
 
 * Expecting to use lambdas or other strong arity implementations for stub
   methods with mis-matched arity is deprecated and support for them will be
@@ -86,26 +87,8 @@ Enhancements:
 * Add a config option to yield the receiver to `any_instance` implementation
   blocks. (Sam Phippen)
 
-### 2.14.6 / 2014-02-20
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.5...v2.14.6)
-
-Bug Fixes:
-
-* Ensure `any_instance` method stubs and expectations are torn down regardless of
-  expectation failures. (Sam Phippen)
-
-### 2.14.5 / 2014-02-01
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.4...v2.14.5)
-
-Bug Fixes:
-
-* Fix regression that caused block implementations to not receive all
-  args on 1.8.7 if the block also receives a block, due to Proc#arity
-  reporting `1` no matter how many args the block receives if it
-  receives a block, too. (Myron Marston)
-
 ### 2.14.4 / 2013-10-15
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.3...v2.14.4)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.3...v2.14.4)
 
 Bug Fixes:
 
@@ -115,7 +98,7 @@ Bug Fixes:
   the usage of modifications (`and_return` etc) (Jon Rowe)
 
 ### 2.14.3 / 2013-08-08
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.2...v2.14.3)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.2...v2.14.3)
 
 Bug Fixes:
 
@@ -123,7 +106,7 @@ Bug Fixes:
   a prepended Module (Bradley Schaefer)
 
 ### 2.14.2 / 2013-07-30
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.1...v2.14.2)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.1...v2.14.2)
 
 Bug Fixes:
 
@@ -133,7 +116,7 @@ Bug Fixes:
   return a test double rather than stub a method (Myron Marston).
 
 ### 2.14.1 / 2013-07-07
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0...v2.14.1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0...v2.14.1)
 
 Bug Fixes:
 
@@ -145,7 +128,7 @@ Bug Fixes:
   in 3.0. (Myron Marston)
 
 ### 2.14.0 / 2013-07-06
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0.rc1...v2.14.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0.rc1...v2.14.0)
 
 Enhancements:
 
@@ -169,7 +152,7 @@ Bug Fixes:
   similar preloading gems (Andy Lindeman).
 
 ### 2.14.0.rc1 / 2013-05-27
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.13.0...v2.14.0.rc1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.13.0...v2.14.0.rc1)
 
 Enhancements:
 
@@ -207,6 +190,7 @@ Bug fixes
   (Luke Imhoff, Jon Rowe)
 * Fix isolation of `allow_message_expectations_on_nil` (Jon Rowe)
 * Use inspect to format actual arguments on expectations in failure messages (#280, Ben Langfeld)
+* Protect against improperly initialised test doubles (#293) (Joseph Shraibman and Jon Rowe)
 
 Deprecations
 
@@ -218,7 +202,7 @@ Deprecations
 * Deprecate `at_least(0).times` and `any_number_of_times` (Michi Huber).
 
 ### 2.13.1 / 2013-04-06
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.13.0...v2.13.1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.13.0...v2.13.1)
 
 Bug fixes
 
@@ -226,7 +210,7 @@ Bug fixes
   `and_yield`, `and_raise`, `and_return` or `and_throw` (Myron Marston).
 
 ### 2.13.0 / 2013-02-23
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.2...v2.13.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.2...v2.13.0)
 
 Bug fixes
 
@@ -256,7 +240,7 @@ Bug fixes
   (Myron Marston).
 
 ### 2.12.2 / 2013-01-27
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.1...v.2.12.2)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.1...v.2.12.2)
 
 Bug fixes
 
@@ -271,7 +255,7 @@ Bug fixes
   versions (Andy Lindeman).
 
 ### 2.12.1 / 2012-12-21
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.0...v2.12.1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.0...v2.12.1)
 
 Bug fixes
 
@@ -283,7 +267,7 @@ Bug fixes
   work properly with constant strings that are prefixed with `::` (Myron Marston).
 
 ### 2.12.0 / 2012-11-12
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.3...v2.12.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.3...v2.12.0)
 
 Enhancements
 
@@ -299,7 +283,7 @@ Deprecations:
   (Neha Kumari)
 
 ### 2.11.3 / 2012-09-19
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.2...v2.11.3)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.2...v2.11.3)
 
 Bug fixes
 
@@ -313,7 +297,7 @@ Bug fixes
   extra time with the wrong arguments (Myron Marston).
 
 ### 2.11.2 / 2012-08-11
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.1...v2.11.2)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.1...v2.11.2)
 
 Bug fixes
 
@@ -325,7 +309,7 @@ Bug fixes
   Marston)
 
 ### 2.11.1 / 2012-07-09
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.0...v2.11.1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.11.0...v2.11.1)
 
 Bug fixes
 
@@ -335,7 +319,7 @@ Bug fixes
   overriden with the null object implementation--`return self`). (Myron Marston)
 
 ### 2.11.0 / 2012-07-07
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.10.1...v2.11.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.10.1...v2.11.0)
 
 Enhancements
 
@@ -360,7 +344,7 @@ Bug fixes
   `Exception` by default, just like ruby does. (Andrew Marshall)
 
 ### 2.10.1 / 2012-05-05
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.10.0...v2.10.1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.10.0...v2.10.1)
 
 Bug fixes
 
@@ -370,14 +354,14 @@ Bug fixes
     * fixed failure of `object.should_not_receive(:message).and_return value`
 
 ### 2.10.0 / 2012-05-03
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.9.0...v2.10.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.9.0...v2.10.0)
 
 Bug fixes
 
 * fail fast when an `exactly` or `at_most` expectation is exceeded
 
 ### 2.9.0 / 2012-03-17
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0...v2.9.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0...v2.9.0)
 
 Enhancements
 
@@ -392,19 +376,19 @@ Bug fixes
 
 ### 2.8.0 / 2012-01-04
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0.rc2...v2.8.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0.rc2...v2.8.0)
 
 No changes for this release. Just releasing with the other rspec gems.
 
 ### 2.8.0.rc2 / 2011-12-19
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0.rc1...v2.8.0.rc2)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.8.0.rc1...v2.8.0.rc2)
 
 No changes for this release. Just releasing with the other rspec gems.
 
 ### 2.8.0.rc1 / 2011-11-06
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.7.0...v2.8.0.rc1)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.7.0...v2.8.0.rc1)
 
 Enhancements
 
@@ -412,7 +396,7 @@ Enhancements
 
 ### 2.7.0 / 2011-10-16
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.6.0...v2.7.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.6.0...v2.7.0)
 
 Enhancements
 
@@ -435,7 +419,7 @@ Bug fixes
 
 ### 2.6.0 / 2011-05-12
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.5.0...v2.6.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.5.0...v2.6.0)
 
 Enhancements
 
@@ -449,7 +433,7 @@ Bug fixes
 
 ### 2.5.0 / 2011-02-05
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.4.0...v2.5.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.4.0...v2.5.0)
 
 Bug fixes
 
@@ -460,14 +444,14 @@ Bug fixes
 
 ### 2.4.0 / 2011-01-02
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.3.0...v2.4.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.3.0...v2.4.0)
 
 No functional changes in this release, which was made to align with the
 rspec-core-2.4.0 release.
 
 ### 2.3.0 / 2010-12-12
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.2.0...v2.3.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.2.0...v2.3.0)
 
 Bug fixes
 
@@ -476,7 +460,7 @@ Bug fixes
 
 ### 2.2.0 / 2010-11-28
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.1.0...v2.2.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.1.0...v2.2.0)
 
 Enhancements
 
@@ -490,7 +474,7 @@ Bug fix
 
 ### 2.1.0 / 2010-11-07
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.1...v2.1.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.1...v2.1.0)
 
 Bug fixes
 
@@ -498,11 +482,11 @@ Bug fixes
 
 ### 2.0.0 / 2010-10-10
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.22...v2.0.0)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.22...v2.0.0)
 
 ### 2.0.0.rc / 2010-10-05
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.22...v2.0.0.rc)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.22...v2.0.0.rc)
 
 Enhancements
 
@@ -516,7 +500,7 @@ Bug fixes
 
 ### 2.0.0.beta.22 / 2010-09-12
 
-[Full Changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.20...v2.0.0.beta.22)
+[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.0.0.beta.20...v2.0.0.beta.22)
 
 Bug fixes
 

data/License.txt

@@ -1,5 +1,6 @@
 (The MIT License)
 
+Copyright (c) 2012 David Chelimsky, Myron Marston
 Copyright (c) 2006 David Chelimsky, The RSpec Development Team
 Copyright (c) 2005 Steven Baker
 

data/README.md

@@ -26,9 +26,8 @@ stubs can be declared on test doubles or real objects using the same syntax.
 rspec-mocks supports 3 forms for declaring method stubs:
 
 ```ruby
-book.stub(:title) { "The RSpec Book" }
-book.stub(:title => "The RSpec Book")
-book.stub(:title).and_return("The RSpec Book")
+allow(book).to receive(:title) { "The RSpec Book" }
+allow(book).to receive(:title).and_return("The RSpec Book")
 ```
 
 You can also use this shortcut, which creates a test double and declares a
@@ -60,7 +59,7 @@ arguments to `and_return`.  The invocations cycle through the list. The last
 value is returned for any subsequent invocations:
 
 ```ruby
-die.stub(:roll).and_return(1,2,3)
+allow(die).to receive(:roll).and_return(1,2,3)
 die.roll # => 1
 die.roll # => 2
 die.roll # => 3
@@ -71,7 +70,7 @@ die.roll # => 3
 To return an array in a single invocation, declare an array:
 
 ```ruby
-team.stub(:players).and_return([stub(:name => "David")])
+allow(team).to receive(:players).and_return([double(:name => "David")])
 ```
 
 ## Message Expectations
@@ -82,11 +81,33 @@ expectation is satisfied. If not, the example fails.
 
 ```ruby
 validator = double("validator")
-validator.should_receive(:validate).with("02134")
+expect(validator).to receive(:validate) { "02134" }
 zipcode = Zipcode.new("02134", validator)
 zipcode.valid?
 ```
 
+## Test Spies
+
+Verifies the given object received the expected message during the course of the
+test. The method must have previously been stubbed in order for messages to be
+verified.
+
+Stubbing and verifying messages received in this way implements the Test Spy
+pattern.
+
+```ruby
+  invitation = double('invitation', :accept => true)
+
+  user.accept_invitation(invitation)
+
+  expect(invitation).to have_received(:accept)
+
+  # You can also use other common message expectations. For example:
+  expect(invitation).to have_received(:accept).with(mailer)
+  expect(invitation).to have_received(:accept).twice
+  expect(invitation).to_not have_received(:accept).with(mailer)
+```
+
 ## Nomenclature
 
 ### Mock Objects and Test Stubs
@@ -112,7 +133,7 @@ For example, in Rails:
 
 ```ruby
 person = double("person")
-Person.stub(:find) { person }
+allow(Person).to receive(:find) { person }
 ```
 
 In this case we're instrumenting Person to return the person object we've
@@ -121,27 +142,25 @@ expectation so that the example fails if `find` is not called:
 
 ```ruby
 person = double("person")
-Person.should_receive(:find) { person }
+expect(Person).to receive(:find) { person }
 ```
 
-We can do this with any object in a system because rspec-mocks adds the `stub`
-and `should_receive` methods to every object, including class objects. When we
-use either, RSpec replaces the method we're stubbing or mocking with its own
+RSpec replaces the method we're stubbing or mocking with its own
 test-double-like method. At the end of the example, RSpec verifies any message
 expectations, and then restores the original methods.
 
 ## Expecting Arguments
 
 ```ruby
-double.should_receive(:msg).with(*args)
-double.should_not_receive(:msg).with(*args)
+expect(double).to receive(:msg).with(*args)
+expect(double).to_not receive(:msg).with(*args)
 ```
 
 You can set multiple expectations for the same message if you need to:
 
 ```ruby
-double.should_receive(:msg).with("A", 1, 3)
-double.should_receive(:msg).with("B", 2, 4)
+expect(double).to receive(:msg).with("A", 1, 3)
+expect(double).to receive(:msg).with("B", 2, 4)
 ```
 
 ## Argument Matchers
@@ -157,81 +176,81 @@ rspec-mocks also adds some keyword Symbols that you can use to
 specify certain kinds of arguments:
 
 ```ruby
-double.should_receive(:msg).with(no_args())
-double.should_receive(:msg).with(any_args())
-double.should_receive(:msg).with(1, kind_of(Numeric), "b") #2nd argument can be any kind of Numeric
-double.should_receive(:msg).with(1, boolean(), "b") #2nd argument can be true or false
-double.should_receive(:msg).with(1, /abc/, "b") #2nd argument can be any String matching the submitted Regexp
-double.should_receive(:msg).with(1, anything(), "b") #2nd argument can be anything at all
-double.should_receive(:msg).with(1, duck_type(:abs, :div), "b")
+expect(double).to receive(:msg).with(no_args())
+expect(double).to receive(:msg).with(any_args())
+expect(double).to receive(:msg).with(1, kind_of(Numeric), "b") #2nd argument can be any kind of Numeric
+expect(double).to receive(:msg).with(1, boolean(), "b") #2nd argument can be true or false
+expect(double).to receive(:msg).with(1, /abc/, "b") #2nd argument can be any String matching the submitted Regexp
+expect(double).to receive(:msg).with(1, anything(), "b") #2nd argument can be anything at all
+expect(double).to receive(:msg).with(1, duck_type(:abs, :div), "b")
                     #2nd argument can be object that responds to #abs and #div
 ```
 
 ## Receive Counts
 
 ```ruby
-double.should_receive(:msg).once
-double.should_receive(:msg).twice
-double.should_receive(:msg).exactly(n).times
-double.should_receive(:msg).at_least(:once)
-double.should_receive(:msg).at_least(:twice)
-double.should_receive(:msg).at_least(n).times
-double.should_receive(:msg).at_most(:once)
-double.should_receive(:msg).at_most(:twice)
-double.should_receive(:msg).at_most(n).times
-double.should_receive(:msg).any_number_of_times
+expect(double).to receive(:msg).once
+expect(double).to receive(:msg).twice
+expect(double).to receive(:msg).exactly(n).times
+expect(double).to receive(:msg).at_least(:once)
+expect(double).to receive(:msg).at_least(:twice)
+expect(double).to receive(:msg).at_least(n).times
+expect(double).to receive(:msg).at_most(:once)
+expect(double).to receive(:msg).at_most(:twice)
+expect(double).to receive(:msg).at_most(n).times
+expect(double).to receive(:msg).any_number_of_times
 ```
 
 ## Ordering
 
 ```ruby
-double.should_receive(:msg).ordered
-double.should_receive(:other_msg).ordered
+expect(double).to receive(:msg).ordered
+expect(double).to receive(:other_msg).ordered
   #This will fail if the messages are received out of order
 ```
 
 This can include the same message with different arguments:
 
 ```ruby
-double.should_receive(:msg).with("A", 1, 3).ordered
-double.should_receive(:msg).with("B", 2, 4).ordered
+expect(double).to receive(:msg).with("A", 1, 3).ordered
+expect(double).to receive(:msg).with("B", 2, 4).ordered
 ```
 
 ## Setting Responses
 
 Whether you are setting a message expectation or a method stub, you can
 tell the object precisely how to respond. The most generic way is to pass
-a block to `stub` or `should_receive`:
+a block to `receive`:
 
 ```ruby
-double.should_receive(:msg) { value }
+expect(double).to receive(:msg) { value }
 ```
 
 When the double receives the `msg` message, it evaluates the block and returns
 the result.
 
 ```ruby
-double.should_receive(:msg).and_return(value)
-double.should_receive(:msg).exactly(3).times.and_return(value1, value2, value3)
+expect(double).to receive(:msg).and_return(value)
+expect(double).to receive(:msg).exactly(3).times.and_return(value1, value2, value3)
   # returns value1 the first time, value2 the second, etc
-double.should_receive(:msg).and_raise(error)
+expect(double).to receive(:msg).and_raise(error)
   #error can be an instantiated object or a class
   #if it is a class, it must be instantiable with no args
-double.should_receive(:msg).and_throw(:msg)
-double.should_receive(:msg).and_yield(values,to,yield)
-double.should_receive(:msg).and_yield(values,to,yield).and_yield(some,other,values,this,time)
+expect(double).to receive(:msg).and_throw(:msg)
+expect(double).to receive(:msg).and_yield(values,to,yield)
+expect(double).to receive(:msg).and_yield(values,to,yield).and_yield(some,other,values,this,time)
   # for methods that yield to a block multiple times
 ```
 
 Any of these responses can be applied to a stub as well
 
 ```ruby
-double.stub(:msg).and_return(value)
-double.stub(:msg).and_return(value1, value2, value3)
-double.stub(:msg).and_raise(error)
-double.stub(:msg).and_throw(:msg)
-double.stub(:msg).and_yield(values,to,yield)
-double.stub(:msg).and_yield(values,to,yield).and_yield(some,other,values,this,time)
+allow(double).to receive(:msg).and_return(value)
+allow(double).to receive(:msg).and_return(value1, value2, value3)
+allow(double).to receive(:msg).and_raise(error)
+allow(double).to receive(:msg).and_throw(:msg)
+allow(double).to receive(:msg).and_yield(values,to,yield)
+allow(double).to receive(:msg).and_yield(values,to,yield).and_yield(some,other,values,this,time)
 ```
 
 ## Arbitrary Handling
@@ -242,8 +261,8 @@ to come with an Array argument that has a specific length, but you don't care
 what is in it. You could do this:
 
 ```ruby
-double.should_receive(:msg) do |arg|
-  arg.size.should eq(7)
+expect(double).to receive(:msg) do |arg|
+  expect(arg.size).to eq 7
 end
 ```
 
@@ -251,7 +270,7 @@ If the method being stubbed itself takes a block, and you need to yield to it
 in some special way, you can use this:
 
 ```ruby
-double.should_receive(:msg) do |&arg|
+expect(double).to receive(:msg) do |&arg|
   begin
     arg.call
   ensure
@@ -268,7 +287,7 @@ the object responds to the message. You can use `and_call_original`
 to achieve this:
 
 ```ruby
-Person.should_receive(:find).and_call_original
+expect(Person).to receive(:find).and_call_original
 Person.find # => executes the original find method and returns the result
 ```
 
@@ -278,7 +297,7 @@ Combining the message name with specific arguments, receive counts and responses
 you can get quite a bit of detail in your expectations:
 
 ```ruby
-double.should_receive(:<<).with("illegal value").once.and_raise(ArgumentError)
+expect(double).to receive(:<<).with("illegal value").once.and_raise(ArgumentError)
 ```
 
 While this is a good thing when you really need it, you probably don't really
@@ -303,8 +322,9 @@ There are many different viewpoints about the meaning of mocks and stubs. If
 you are interested in learning more, here is some recommended reading:
 
 * Mock Objects: http://www.mockobjects.com/
-* Endo-Testing: http://www.mockobjects.com/files/endotesting.pdf
-* Mock Roles, Not Objects: http://www.mockobjects.com/files/mockrolesnotobjects.pdf
+* Endo-Testing: http://stalatest.googlecode.com/svn/trunk/Literatur/mockobjects.pdf
+* Mock Roles, Not Objects: http://jmock.org/oopsla2004.pdf
+* Test Double: http://www.martinfowler.com/bliki/TestDouble.html
 * Test Double Patterns: http://xunitpatterns.com/Test%20Double%20Patterns.html
 * Mocks aren't stubs: http://www.martinfowler.com/articles/mocksArentStubs.html