[Pharo-project] i can has TestCase>>#assert:equals: ?
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
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 <oscar@iam.unibe.ch> 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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, Apr 10, 2009 at 9:06 PM, Oscar Nierstrasz <oscar@iam.unibe.ch> wrote:
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?
No, there is no downside and no possible improvement. All other xUnit frameworks have that for a long time. I think Keith's version of SUnit has that too. -- Damien Cassou http://damiencassou.seasidehosting.st
SUnit should have this methods for years Alexandre On 10 Apr 2009, at 21:06, Oscar Nierstrasz 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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
participants (4)
-
Alexandre Bergel -
Damien Cassou -
Michael Roberts -
Oscar Nierstrasz