> > > PS: Ok, I know, there is the error string. > that nobody never reads :-) I think in Smalltalk it does not make too much sense to have assert:equals:, like you say, it does not add value... but in those "parenthesis languages" were number are not objects and etc... well, they need it :-)
> > 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 > > -- *Hernán Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: [email protected] site: http://www.10Pines.com <http://www.10pines.com/>* Address: Paraguay 523, Floor 7 N, Buenos Aires, Argentina
