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

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? Thanks. Sean -- 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.