assert{ 2.0 }
Date : 02 11 2008 Category : Web
O'Reilly Network Articles and Weblogs
This is a problem in all of unit testing - the cobbler's
own children always get the worst shoes! Our platform knows
everything we know about assert x == 42, but it
can't tell us everything for one reason: Languages optimize
for the needs of production code, not test code. So our
customers will always get better tools than we get!
Ruby supplies just enough reflection for an assertion to
reconstruct a block of code.