On Tue, Jun 21, 2011 at 6:05 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:

On Tue, Jun 21, 2011 at 10:32 PM, Bernardo Ezequiel Contreras <vonbecmann@gmail.com> wrote:

did you check this
http://code.google.com/p/pharo/issues/detail?id=4129
?

Yes, I was the gulty. But I am still on favor. So I don't undersatnd Sean's problem.
�

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.

--
Mariano
http://marianopeck.wordpress.com