Displaying 1 result from an estimated 1 matches for "___no_arg".
2007 Jan 29
3
Bug in should_not_be - What else to use?
Hi!
I just stumbled over a possible bug in 0.7.5.1:
`1.should_not_be == 1` does not fail.
I took a look into the code and figured out, that this is caused by
Not.be() using :no_arg instead of :___no_arg. The expected argument of
the method be() in Not is passed from should_not_be() with :___no_arg.
Not.be() is marked with "Gone for 0.9", so I assume that "should_not_be
==" shouldn''t be used at all, right? So what else to use, when testing
of "==" is required...