On Tue, Jun 21, 2011 at 7:16 PM, Sean P. DeNigris <span dir="ltr">&lt;<a href="mailto:sean@clipperadams.com">sean@clipperadams.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

In my unit test, I want to make sure that my output equals the<br>
expectedOutput, but:<br>
 �� ��TestCase&gt;&gt;assert: expected equals: actual<br>
<br>
It feels wrong to me. It seems that I want to make an assertion about my<br>
class&#39;s behavior and I would like to write:<br>
 �� ��self assert: output equals: expectedOutput.<br>
<br>
What do you all think?<br></blockquote><div><br></div><div>Personnally I prefer��</div><div><br></div><div>assert: expected equals: actual��</div><meta charset="utf-8"><div><br></div><div>because the first thing I have to think about is what I expect, not how to get it. So for me it feels more natural to write it this way.</div>

<div><br></div><div>Laurent.</div><div>��</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Thanks.<br>
Sean<br>
<font color="#888888"><br>
--<br>
View this message in context: <a href="http://forum.world.st/assert-equals-feels-backwards-tp3614760p3614760.html" target="_blank">http://forum.world.st/assert-equals-feels-backwards-tp3614760p3614760.html</a><br>
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.<br>
<br>
</font></blockquote></div><br>