[rspec-devel] subject.should_be true
dastels at daveastels.com
Sun Oct 15 23:50:52 EDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
On 15-Oct-06, at 11:31 PM, David Chelimsky wrote:
> As things stand now, the following will all pass:
> true.should_be true
> "true".should_be true
> "false".should_be true
> 3.should_be true
> My feeling is that "should_be true" should only pass if it returns
> boolean true even though ruby says that non-nil/non-false is true.
> Anybody else?
I remember having this discussion a while ago.
I still think "should_be true" should reflect the Ruby concept of
"true"... the principle of least surprise
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
-----END PGP SIGNATURE-----
More information about the rspec-devel