RE: [Transmogrify-development] Starting Unit Tests

[Nascif Abousalh-N. <na...@no...>]

I understand. Hopefully I'll have some more time soon to remove the
dependency on gnuserv, which should make it easier for you to get it to
work.
As for the bsh/JDE dependency, I think I can't get it to work without them -
unless.... unless we make a "refactoring server" that implements Hook and
provides a socket-based interface. It could talk directly to Emacs without
using Java(or the Beanshell) at all. Then again, it is yet another JVM
running in your machine, and another editor-to-library API to define... 

Regards,
	Nascif


> -----Original Message-----
> From: John P N Pybus [mailto:joh...@zo...]
> Sent: Friday, October 12, 2001 12:30 PM
> To: tra...@li...
> Subject: [Transmogrify-development] Starting Unit Tests
> 
> 
> On Wednesday 12 Sep 2001 6:23 pm, Andrew McCormick (smileyy) wrote:
> > On Wed, 12 Sep 2001, John P N Pybus wrote:
> > > [snip]                                                    
>              Do
> > > you know of a way to make the junit test's GUI close 
> automatically if all
> > > the tests complete successfully?
> >
> > The best thing I can think of is to use the JUnit's text UI 
> instead of the
> > Swing UI.  In the particular test suite that you're running, change:
> >
> >   junit.swingui.TestRunner.run( ... );
> >
> > to
> >
> >   junit.textui.TestRunner.run( ... );
> >
> > I can't immediately think of a way to make this a project-wide
> > configurable option, though.
> 
> I've added two new classes to net/sourceforge/transmogrify/test/.   
> TestStarter uses a system property to decide which TestRunner 
> to run.  I've 
> edited every test in the tree which had a main() to use 
> TestStarter.startRun(someTestClass.class), rather than 
> junit.swingui.TestRunner.run(someTestClass.class).  I've 
> tested them all[1] 
> by running every test possible standalone, as well as as part 
> of their 
> respective TestSuite.
> 
> I've also added a class ExitingTestRunner, which subclasses 
> junit.swingui.TestRunner to provide a version which exits at 
> the end of a 
> successful run.  Now I can get my way - a pretty green/red 
> bar, and ant 
> completing its build without blocking if the bar stays green.
> 
> Unless you have any objections, I'll check in these changes.
> 
> > > I don't know about an IDE (I tend to use Xemacs for all 
> my developments),
> > > but a standalone app to browse source and apply 
> refactorings, would be a
> > > great idea.
> >
> > That would the general idea -- something that integrates well with
> > "command-line" development tools.
> 
> Since I've so far failed in my various attempts to get 
> Transmogrify to work 
> wth Xemacs.  I don't have a copy of JBuilder, and haven't had 
> time to install 
> plain Emacs with all the required libs (sorry Nascif), I've 
> started putting 
> together a simple swing based file viewer with Hook to apply 
> refactorings.  
> So far I've only got a couple of the refactorings hard-wired 
> into it's menu.  
> Once I've added a bit more code to build the menus from the 
> .xml files as the 
> jbuilder hook does, I'll add this to the project so you can 
> have a look.
> 
> Yours,
> 
> John Pybus
> 
> [1] In the process I came across NameAmbiguityTest, which I 
> notice doesn't 
> pass, tut tut. ;-)
> 
> _______________________________________________
> Transmogrify-development mailing list
> Tra...@li...
> https://lists.sourceforge.net/lists/listinfo/transmogrify-development
>