Re: Mocking framework

[Ola Bini <ola.bini@gmail.com>]

Brian Guthrie wrote:
> Hi all,
>
> I've taken a stab at building out a mocking framework for ISpec, and
> the results are up on my fork at
> http://github.com/bguthrie/ioke/tree/master.  Here's what it supports
> so far:
>
>  - stubs
>  - mocking with simple argument matching (expects("foo") with(5),
> expects("foo") with (5, :bar))
>  - mocking with number-of-times-called verification
>  - ISpec-friendly "foo should receive" syntax or Mocha-friendly "foo
> expects" syntax
>  - unmocking of the object in question after verification is complete
>
> Example:
>
> it("should make a call to the remote service",
>   User should receive("find") with(:all) andReturn([])
> ) ... ISpec ExpectationNotMet("expected find to be called 1 time(s)")
>   
Good work.

I keep thinking that there should be a better way of expressing this 
that isn't so tied to the verbose Ruby-DSLs. Something like:

User should receive find(:all) andReturn([])

That should be pretty easy to implement.

Cheers

--
Ola Bini (http://olabini.com) 
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

"Yields falsehood when quined" yields falsehood when quined.