0.01
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
Assert that an object responds to a method before asserting that the method is received.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Development

>= 0
>= 0

Runtime

~> 2.14
~> 2.14.6
 Project Readme

Code Climate

BetterReceive

Test drive new functionality and prevent bugs by asserting objects respond to methods when mocking/stubbing.

Installation

$ gem install better_receive

Usage

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.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

To Do

  • support arrity checks with #responds_to
  • support options other than Ruby 1.9.2+ and RSpec