Iâve seen this problem tons of times since Pharo4. But the worst is that I never found a way to reproduce it. To me there is some side effect somewhere. Because it does not happen in a fresh image, but once you have it, you have it all the time.
On 24 nov 2015, at 1:49 p.m., Ben Coman <btc@openinworld.com> wrote:
On Tue, Nov 24, 2015 at 7:32 AM, Esteban A. Maringolo <emaringolo@gmail.com <mailto:emaringolo@gmail.com>> 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