Community
Participate
Working Groups
Dear Eclipse dev team, Sorry if I didn't check the correct component - not sure which is the most appropriate one. This is about the testing framework used for eclipse tests, specifically the plugin org.eclipse.test. I've been recently trying to implement some tests on an Eclipse plugin, which does the following: do some work launch a bunch of UI jobs wait for the UI jobs to finish checks some stuff The problem is that with the current version of the test framework, ui tests are always run from a UIJob, so the secondary jobs of the tests can't be started while the test is running. Looking a bit at the eclipse framework, I could add a parameter red by the org.eclipse.test.UITestApplication class. Bascially, if the eclipse application is launched with "-testJob worker", it launches the tests in a non ui job, as opposed to the default behavior. That seems to solve my problem so far. So I'm submitting the patch to the eclipse community (attached) to see if it make sense to be integrated. Best regards, Quentin Ochem
Created attachment 113889 [details] Patch to UITestApplication
This enhancement request seems to be addressed by the latest eclipse 3.5M5: > JUnit plug-in tests in non-UI thread > You can now launch JUnit Plug-in tests in a non-UI thread. A check box has been > added to the Test tab to specify whether tests should run in the UI thread. If that's the case (e.g., this would be accessible in batch mode as well), then I guess this entry should be marked as resolved.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
