From: Dave Thomas <Dave@...>
Date: 2002-07-27T21:40:33+09:00
Subject: Re: [PATCH] object.c ruby.h (fwd)

Masaki Suketa <masaki.suketa@nifty.ne.jp> writes:

>   str = 'foo'
>   str += 'bar'
>   assert('foobar', str) #  str must be 'foobar'
> 
> The above code is not correct(assert_equal should be used instead of
> assert). But older version of RubyUnit can not notice it because
> 1st argument is true.
> 
> I am not sure which behavior is better. Can I ignore this kind of 
> confusion? Any idea?

There's not much we can do if people call the incorrect method :)

If this is a problem that occurs frequently, then perhaps we could go
the way JUnit went and deprecate 'assert' in favor of 'assert_true'
(or possibly 'assert_truth').


Cheers


Dave