[mocha-developer] With Parameter Block

Zach Moazeni zach.lists at gmail.com
Fri Jun 22 12:43:47 EDT 2007


Yeah that's fine with me. I'm really swamped now, but I'll try and  
work out something soon and submit a patch of what I'm thinking.

I do want give kudos to the team for developing a nice mocking  
library. It hasn't been a silver bullet, but it does make my testing  
much easier.


On Jun 22, 2007, at 8:26 AM, Dan North wrote:

> James Mead wrote:
>> Hi Zach,
>> I'm not fixed on the idea of the block check going away. It's  
>> great to have
>> your example usage. You are right that readability is one  
>> advantage of the
>> parameter matcher classes, but another benefit is hopefully more  
>> useful
>> error messages. Maybe the solution is to have a custom matcher  
>> which takes a
>> block. What do you think?
>> I'll give it some more thought.
> I agree - having a custom matcher that knows about procs is a cleaner
> solution than having the whole proc thing baked into expectations.
> Expecting a proc is an edge case when you are mostly mocking services.
> It's normally simple value objects like strings that get passed in as
> parameters.
> Cheers,
> Dan
> _______________________________________________
> mocha-developer mailing list
> mocha-developer at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mocha-developer

More information about the mocha-developer mailing list