I have used something similar elsewhere. +1 in general. The only gotcha is making sure people don't use it for comparing doubles. If there are not methods already I would add some form of assert:equals:tolerance: or something like that.
cheers, Mike On Fri, Apr 10, 2009 at 8:06 PM, Oscar Nierstrasz <[email protected]> wrote: > > Hi folks, > > 90% of my tests just test equality of a result to an expected value, > so I waste time trying to find out what the mismatch is. Would be > nice to have this method in SUnit: > > assert: result equals: expected > result = expected > ifFalse: [self signalFailure: 'Assertion failed: (' , result > asString , ') ~= (' , expected asString , ')'] > > Does anyone see a downside, or possible improvements? > > - on > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
