On 23 May 2013, at 16:34, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-05-23, at 16:26, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 23 May 2013, at 15:59, Camillo Bruni <camillobruni@gmail.com> wrote:
why? To me this does not make sense. I'd expect
Error subclass: #AssertionFailure
Yeah, I have asked myself the same question quite often.
I often write self assert: <some condition> in production code, but then an #on:do: handler specifying only Error won't catch the AssertionFailure exceptions.
exactly! I'm going to propose a fix, because I hate to write Error,AssertionFailure :P
I would guess it has something to do with SUnit logic ?
Must be some strange leftover, since in interactive mode there is no distinction between Halt and any other Error.
But doesn't TestRunner react differently on AssertionError as opposed to other Errors ? The former are called 'Failures', the latter 'Errors'...