IMO having the expected value before is the right way ! Do you TDD ? It makes a lot of sense for me to write assert: expected equals: actual. Am I alone ?
If you do TDD, you have first to decide what you expect. You don't know how to get it because the code doesn't exist yet. So you usually I write self assert: 'i want this' equals: then stop because I have to think about the interface / selectors / object I want. So it matches the flow of thought when I'm writing tests. And the other weird thing is that with this "fix" I now have to change hundred of tests I've written to be semantically correct !!!! Laurent. On Wed, Jun 22, 2011 at 12:39 AM, Sean P. DeNigris <[email protected]>wrote: > > Mariano Martinez Peck wrote: > > > > I don't understand Sean's problem. > > > > Still using 1.2.2 :) Thanks for fixing it. > > Sean > > -- > View this message in context: > http://forum.world.st/assert-equals-feels-backwards-tp3614760p3615548.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >
