Another nice integration would be to use the BeanShell to provide a similar
functionality than the one in the Swing version: browsing the hierachy of Suites and
TestCases, using name completion or a dired-like window to make selections and
execute them .
"Abousalh-Neto, Nascif" wrote:
> Some suggestions, then:
> - Some specialized templates for TestCases would be useful.
> - A preferred way to organize directories and integrate the TestCase classes
> in the package project file.
> - Some jde commands to launch the JUnit text mode and capture the output,
> maybe even jumping to the offending instruction from the exception dump.
>
> What do you think?
>
> Paul Kinnucan wrote:
>
> > At 03:45 PM 5/15/00 -0400, you wrote:
> > >Hi,
> > >
> > > I'm starting to use JUnit for my unit testing, and I was wondering
> > >if anybody has some thoughts on how to integrate it better with JDE. I
> > >think that there is a lot of ways - keybinds to automatically launch
> > >tester, project settings, directory structures, etc. - to make the two
> > >frameworks work better together.
> > >
> >
> > I think this is a good idea as I use JUnit myself. I'm open to suggestions.
> >
> > - Paul
> >
> > ------------------------------------------------------------
> > TECH SUPPORT POLICY
> >
> > I respond only to requests that contain a complete problem report. The
> > easiest way to ensure that your report is complete is to include the output
> > of the JDE->Help->Submit Problem Report command in your request.
> >
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > JDE website: http://sunsite.auc.dk/jde/
> >
> > JDE mailing list archive:
> > http://www.mail-archive.com/[email protected]/maillist.html
