Test drive new functionality and prevent bugs by asserting objects respond to methods when mocking/stubbing.
$ gem install better_receive
class Foo; end foo = Foo.new foo.better_receive(:bar) # or foo.better_stub(bar: 1, baz: 2) # or Foo.any_instance.better_receive(:bar).with(:wibble) # or foo.better_not_receive(:bar_baz)
Any of these situation will raise an error because instances of Foo do not respond to :bar.
After the initial extra assertion, they continue to act like regular RSpec mocks/stubs.
If you are using a version of RSpec < 2.14, lock to BetterReceive version 0.5 or earlier.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Added some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request
- support arrity checks with #responds_to
- support options other than Ruby 1.9.2+ and RSpec