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

David Chelimsky dchelimsky at gmail.com
Mon Jan 29 07:31:36 EST 2007


On 1/29/07, Tobi <listaccount at e-tobi.net> wrote:
> 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.

Already in the plan. It won't print warnings in 0.8.0, but it will be
shortly thereafter, and well before the deprecated methods are
removed.

>
> Tobias
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>


More information about the rspec-users mailing list