Thanks David!
I will try the new matcher after I migrate to rspec 1.2.x :) But
seems a lot easier to create . Really liking it!
Emmanuel
On Mar 25, 2009, at 6:00 PM, David Chelimsky wrote:
On Wed, Mar 25, 2009 at 7:32 PM, Zach Dennis
wrote:
On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pin
On Wed, Mar 25, 2009 at 7:32 PM, Zach Dennis wrote:
> On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pinault wrote:
>> Hi,
>>
>>
>> Is there way to generate a better error messages when I have a matcher in my
>> step like
>>
>> 1.should == 0 => would fail with expected 1, got 0
>>
>> I would like to
On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pinault wrote:
> Hi,
>
>
> Is there way to generate a better error messages when I have a matcher in my
> step like
>
> 1.should == 0 => would fail with expected 1, got 0
>
> I would like to add more details to that error? Especially , in my case ,I
> am
Hi,
Is there way to generate a better error messages when I have a matcher
in my step like
1.should == 0 => would fail with expected 1, got 0
I would like to add more details to that error? Especially , in my
case ,I am using the include? matcher.
Thanks
Emmanuel
_
