|Eclipse JUnit Plug-in Test [message #598632]
||Fri, 26 June 2009 13:28
| Flavio Donze
Registered: July 2009
Hello pde team|
Right now I'm creating a JUnit Plug-in Lanuch for my server environment.
Doing that, I noticed a few things.
First, since I want to test a server application I don't need any UI
plug-ins. The org.eclipse.test plug-in, actually the UITestApplication
class has dependencies on org.eclipse.ui.ide.application and
org.eclipse.ui. They then have a whole dependency tree on other UI
This does not affect my tests I just think it's kind of ugly.
So I was wondering if maybe the plug-in should be split up in
org.eclipse.test and org.eclipse.test.ui? What do you think of this?
Second, the launch seems to ignore my start levels if I don't set the
"Auto-Start" to "true". Even though the "Default Auto-Start" option is set
Launching in Headless Mode, Test runner JUnit 3.
Is this an intended behavior or should I file a bug report?
Prozessmanagement und Qualitätsmanagement Software QMS/IMS
Powered by FUDForum
. Page generated in 0.01314 seconds