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

Guillermo Polito guillermopolito at gmail.com
Tue Jun 21 15:56:36 EDT 2011


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 at 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20110621/4df86836/attachment-0001.html>


More information about the Pharo-dev mailing list