[rspec-users] Bug in should_not_be - What else to use?

Tobi listaccount at e-tobi.net
Mon Jan 29 04:41:01 EST 2007


David Chelimsky wrote:
> Try should_not == 1
>   

Ok. It just gives me a not so nice to read failure message:

"1 should not == 1"  compared to  "1 should not be == 1"

Maybe the "Gone for 0.9"-methods should print a deprecation warning in
one of the next releases.

Tobias



More information about the rspec-users mailing list