Why don't you just use #assert: and #=? This is much shorter and the description string is not really worth the troubles, isn't it :-)
Lukas PS: Ok, I know, there is the error string. On 21 June 2011 22:45, Max Leske <[email protected]> wrote: > +1 > > > On 21.06.2011, at 19:16, Sean P. DeNigris wrote: > >> 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. >> > > > -- Lukas Renggli www.lukas-renggli.ch
