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)