[Pharo-users] Feedback on #assert: vs. #assert:equals:

Nahuel Garbezza n.garbezza at gmail.com
Wed Oct 21 21:21:22 EDT 2015


Hi everyone,

I'm using Pharo for teaching and we use TDD since the beginning. I've
noticed that if you use #assert: on a test, like this:

self assert: object messageReturningBoolean

It gives you strange results in terms of feedback if the result is not a
boolean. I would expect an AssertionFailed (yellow test) but I got a
NonBooleanReceiver (red test).

What we do in our course is to write the assertion like this:

self assert: object messageReturningBoolean equals: true

So we got a "expected true but was <other object>" error which is a lot
more helpful to the students.

I was thinking that is better to have #assert: implementation based on
#assert:equals:. It is like saying #assert:equals: is the "primitive"
assertion message, which makes sense to me since you are always comparing
if an object is equal to another, there's no reason to handle the booleans'
case differently.

What do you think?

Thank you!

Nahuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20151021/9858037e/attachment.html>


More information about the Pharo-users mailing list