Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327970

Summary: Automated test .launch configs must not define list of workspace bundles
Product: [RT] ECF Reporter: Markus Kuppe <bugs.eclipse.org>
Component: ecf.testAssignee: Markus Kuppe <bugs.eclipse.org>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: slewis
Version: 3.3.0   
Target Milestone: 3.4.0   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
mylyn/context/zip none

Description Markus Kuppe CLA 2010-10-16 05:50:27 EDT 
"Launch with:" has to be set to "all workspace and enabled target plug-ins" in launch configs that are used for automated testing. Buckminster makes sure all required bundles are either materialized to the workspace or targetplatform.
Comment 2 Markus Kuppe CLA 2010-10-16 05:59:28 EDT 
Created attachment 181033 [details]
mylyn/context/zip
Comment 3 Scott Lewis CLA 2010-10-16 07:25:40 EDT 
Setting 'all plugins in workspace' makes it rather difficult to run these tests in local workspaces...why does it have to be set for automated testing?
Comment 4 Markus Kuppe CLA 2010-10-17 03:12:00 EDT 
(In reply to comment #3)
> Setting 'all plugins in workspace' makes it rather difficult to run these tests
> in local workspaces...why does it have to be set for automated testing?

What is difficult about it?
Comment 5 Scott Lewis CLA 2010-10-17 09:59:31 EDT 
(In reply to comment #4)
> (In reply to comment #3)
> > Setting 'all plugins in workspace' makes it rather difficult to run these tests
> > in local workspaces...why does it have to be set for automated testing?
> 
> What is difficult about it?

I've got a lot of plugins in my own workspace(s) that shouldn't be included in running a test of generic remote services.  Including them by default means that the test can be broken, the output more complex/spurious, or just slowed down significantly because it's in the same workspace (with the 'all plugins in workspace' checked).  This will of course also be true for others that try to run the automated tests locally.

Further I think it would just be clearer for everyone if every automated test explicitly named the bundles/fragments that is used/depended upon to be run...but I understand this is more work...so in any case, I'll create local launch configs.