[Pharo-project] #assert:equals: feels backwards

Sean P. DeNigris sean at clipperadams.com
Tue Jun 21 13:16:38 EDT 2011

In my unit test, I want to make sure that my output equals the
expectedOutput, but:
    TestCase>>assert: expected equals: actual

It feels wrong to me. It seems that I want to make an assertion about my
class's behavior and I would like to write:
    self assert: output equals: expectedOutput.

What do you all think?


View this message in context: http://forum.world.st/assert-equals-feels-backwards-tp3614760p3614760.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

More information about the Pharo-dev mailing list