Okay, to throw in a little more oil into the fire: I just realized that
TestRunner is broken even worse with all of the magic background process
stuff. Most recent example: If you debug an individual test #tearDown is
actually being called right away. Example:

FooTest>>setUp
    testStarted := false.

FooTest>>testError
    testStarted := true.
    self error: 'failure simulation'.

FooTest>>testFailure
    testStarted := true.
    self assert: false

FooTest>>cleanUp
    self assert: testStarted.

Now run the test once; it will show one failure and one error. Fine. Now
click on each of the tests to get the debugger. Bummer! Duh ... sure
explains why I had such problems when I wrote the ClassBuilderFormatTests.
So whatever background process magic is in test runner, no matter how
useful, it is utterly broken.

BTW, SUnit *used* to have tests itself, are they anywhere?

Cheers,
  - Andreas

----- Original Message ----- 
From: "Julian Fitzell" <julian at beta4.com>
To: "The general-purpose Squeak developers list"
<squeak-dev at lists.squeakfoundation.org>
Sent: Wednesday, March 03, 2004 6:47 PM
Subject: Re: [BUG][FIX] TestRunner UI interaction


> Shouldn't need to give TestRunner a world, just need an appropriate
> TestResource that Morphic tests can use...  or a morphic test superclass
> that provides it in setup... right?
>
> Julian
>
> Andreas Raab wrote:
> > Sure, the only question is: How much time are willing to invest?! For
> > example, the Right Way (tm) to deal with this is to give TestRunner its
"own
> > world" in which it could run these tests. Simple as that. It would mean
that
> > any Morphic related tests would just see their own "World" (possibly
even
> > embedded into TestRunner) so if you run these in the background you
wouldn't
> > be affected by any suddenly popping up windows or similar. Alas, I just
> > don't have time for it...
>
> -- 
> julian at beta4.com
> Beta4 Productions (http://www.beta4.com)
>
>