Re: [jdt-debug-dev] Running individual test classes

[Jared Burns <jaredburns@xxxxxxx>]

The AutomatedSuite normally calls the ProjectCreationDecorator (badly named?) 
tests which set up the project. My change to AbstractDebugTest was to call 
the ProjectCreationDecorator in the constructor if the project isn't set up.

I don't see any other setup that's required. Am I missing something?

An example of a test class that fails outside the AutomatedSuite is 
ConditionalBreakpointsTests. The wierdest thing is that I can comment out 
every test except this one in the AutomatedSuite and it will work. This seems 
to imply that there's no other setup required. But if I run it on its own it 
hangs.

- Jared

On Wednesday 18 June 2003 11:24 am, Darin Wright wrote:
> Does the test harness import/build the test projects and launch
> configurations required to launch?
>
> Darin
>
>
>
>
>
> Jared Burns <jaredburns@xxxxxxx>
> Sent by: jdt-debug-dev-admin@xxxxxxxxxxx
> 06/18/2003 11:08 AM
> Please respond to jdt-debug-dev
>
>
>         To:     jdt-debug-dev@xxxxxxxxxxx
>         cc:
>         Subject:        [jdt-debug-dev] Running individual test classes
>
>
>
> I've released a change to AbstractDebugTest that lets us run individual
> test
> classes by selecting the class and using Run As->JUnit Plug-in Test. This
> works fine for tests that don't involve launching, but tests that involve
> launching don't come back.
>
> Can anyone take a look at this and see if there's an obvious cause?
>
> Thanks,
> - Jared
>
> _______________________________________________
> jdt-debug-dev mailing list
> jdt-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev