From: Marko Schulz <in6x059@...>
Date: 2002-03-21T03:51:23+09:00
Subject: Re: Test::Unit GTk GUI

On Thu, Mar 21, 2002 at 03:02:44AM +0900, Bil Kleb wrote:
> "Nathaniel Talbott" <nathaniel@talbott.ws> wrote:
> > 
> > I haven't used a GUI test runner for Ruby in ages, because there is not
> > a safe way to load in changes to a test runner after it is already
> > launched. This means the GUI has to be closed down and re-opened each
> > time something is changed,
> 
> Do the JUnit or SUnit GUIs also suffer from this problem? 

Junit implements its own ClassLoader to load changed classes. It is a
constant source of problems. Probably the reloading feature only works
flawlessly in VAJ, where VAJ is responsible (and capable) or reloading
classes in a running VM.

I think in Smalltalk it is quite easy to reload classes on the fly,
but I am not sure, I never used it.

-- 
marko schulz