Thanks for the answers, and for addressing this soon :)
I would like to participate on the sprint but I can't make it this time.
Nahuel
2015-10-22 12:15 GMT-03:00 Alexandre Bergel :
> Dear Nahuel,
>
> I think you are raising in excellent point.
> I think that assert: should raise an assertion er
Dear Nahuel,
I think you are raising in excellent point.
I think that assert: should raise an assertion error when a non-boolean is
provided.
I have added an entry:
https://pharo.fogbugz.com/f/cases/16847/assert-should-not-raise-an-error-with-a-non-boolean-argument
Tomorrow we have a sprint, t
Le 22/10/15 12:03, Peter Uhnák a écrit :
This is why I pretty much stopped using #assert: altogether,
however note that sometimes it is better to avoid boolean completely,
because the feedback of it is low
Imagine:
self assert: collection isEmpty
versus
self assert: collection size equals
This is why I pretty much stopped using #assert: altogether,
however note that sometimes it is better to avoid boolean completely,
because the feedback of it is low
Imagine:
self assert: collection isEmpty
versus
self assert: collection size equals: 0
versus
self assert: collection asArray eq
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 AssertionFaile
