yes, there was. It is like that because that is how it is in JUnit.... everybody agreed it was rare �and if I'm not wrong, was going to be changed

On Tue, Jun 21, 2011 at 4:56 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:
I remember a thread about this not long ago...� Try searching the history :)

Guille


On Tue, Jun 21, 2011 at 2:16 PM, Sean P. DeNigris <sean@clipperadams.com> 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.





--
Hern�n Wilkinson
Agile Software Development, Teaching & Coaching
Mobile: +54 - 911 - 4470 - 7207
email: hernan.wilkinson@10Pines.com
site:�http://www.10Pines.com
Address: Paraguay�523, Floor 7 N, Buenos Aires, Argentina