On Tue, Nov 24, 2015 at 7:32 AM, Esteban A. Maringolo <[email protected]>
wrote:
> I'm trying to debug a failing test case in Pharo 5, but for some reason in
> certain tests I can't see the full stack, so basically I can't fix nor
> diagnose the failing test within the debugger because I only get the assert
> notification.
>
>
>
> This doesn't happen in Pharo 4, there seems to be a refactoring of the
> TestCase hierarchy, but I don't know how it affects the exception handling,
> which in the case of Glorp seems to not be very orthodox.
>
> Regards!
>
>
> Esteban A. Maringolo
>
Possible workaround hack is to remove some of the conditions
from #on:do: so you get a debugger straight away on the original error
rather than storing it for later.
TestResult>>runCase: aTestCase
[
aTestCase announce: TestCaseStarted withResult: self.
aTestCase runCase.
aTestCase announce: TestCaseEnded withResult: self.
self addPass: aTestCase]
on: self class failure , self class skip, self class warning, self class
error
do: [:ex | ex sunitAnnounce: aTestCase toResult: self]
cheers -ben
