Bug 493390 - JUnit Plug-in Test launch should only include required plugins
Summary: JUnit Plug-in Test launch should only include required plugins
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-10 17:44 EDT by Sam Davis CLA
Modified: 2016-05-11 04:59 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Davis CLA 2016-05-10 17:44:36 EDT 
When using Run as JUnit Plugin Test, all plugins in the workspace and target platform are included in the launch. Not only is this incredibly slow, in many cases the tests don't even run due to interference from other other plugins. The launcher should include only the selected plugin and its dependencies.

Because of this issue, Run as JUnit Plugin Test does not work for me all. My workaround is to have a "template" JUnit Plugin launch configuration with a minimal set of plugins, which I duplicate and edit whenever I want to run a different test. But even then, selecting the project to run does not add it to the plugins included in the launch - I have to also go to the Plugins tab and add that plugin and its dependencies. It would be nice if selecting a project to run would also add that plugin and its dependencies.
Comment 1 Jay Arthanareeswaran CLA 2016-05-11 01:53:46 EDT 
Not sure where this belongs, for now moving to UI.
Comment 2 Dani Megert CLA 2016-05-11 04:59:16 EDT 
If you use features, you could try the feature based launch.