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

Bug 289521

Summary:	Update test deployment documentation.
Product:	z_Archived	Reporter:	Paul Slauenwhite <paulslau>
Component:	TPTP	Assignee:	Paul Slauenwhite <paulslau>
Status:	CLOSED WONTFIX	QA Contact:	Kathy Chan <kathy>
Severity:	normal
Priority:	P2	CC:	paulslau
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Paul Slauenwhite

2009-09-15 15:40:24 EDT

Update test deployment documentation.

The following updates are required for the test deployment documentation (see http://help.eclipse.org/galileo/topic/org.eclipse.hyades.test.doc.user/tasks/tdeploymentintro.htm):

1) Deployments do not require an artifact-location pair or artifact to execute a test.  In effect, test execution with a deployment without an artifact-location pair or artifact is the same as executing a test with just a location.  This the the same as using the local_deployment, except the user can define the target host.  This eliminates regenerating an artifact and the CLASSPATH general properties whenever the version of the plug-in under test changes.  This is a common use case, with the artifact used for custom deployments.

2) Test execution only uses the first artifact, location, and artifact-location pair in a deployment.  The second and subsequent artifacts, locations, and artifact-location pairs are ignore.  Requires verification.

3) When test suites references test suites/cases located in another plug-in project, the dependencies must be reexported in the referenced plug-in project's manifest (see http://help.eclipse.org/galileo/topic/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/dependencies.htm) when running the referencing test suite (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=289348).

Requires translation.

Comment 1 Paul Slauenwhite

2009-09-17 06:37:45 EDT

Regarding #1, the current design allows tests to be executed with deployments without an artifact-location pair or artifact when using ASF.  However, the UI does not allow the user to select the deployment in the launch configuration dialog that does not have an artifact-location pair:

org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment)

Consider relaxing this constraint in the UI.

Comment 2 Paul Slauenwhite

2009-11-13 07:46:14 EST

(In reply to comment #1)
> Regarding #1, the current design allows tests to be executed with deployments
> without an artifact-location pair or artifact when using ASF.  However, the UI
> does not allow the user to select the deployment in the launch configuration
> dialog that does not have an artifact-location pair:
> 
> org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment)
> 
> Consider relaxing this constraint in the UI.

Covered in defect 236308.

Comment 3 Paul Slauenwhite

2009-11-17 09:06:13 EST

(In reply to comment #2)
> (In reply to comment #1)
> > Regarding #1, the current design allows tests to be executed with deployments
> > without an artifact-location pair or artifact when using ASF.  However, the UI
> > does not allow the user to select the deployment in the launch configuration
> > dialog that does not have an artifact-location pair:
> > 
> > org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment)
> > 
> > Consider relaxing this constraint in the UI.
> 
> Covered in defect 236308.

Ignore (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=236308#c3).

Comment 4 Paul Slauenwhite

2009-11-17 09:43:58 EST

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Regarding #1, the current design allows tests to be executed with deployments
> > > without an artifact-location pair or artifact when using ASF.  However, the UI
> > > does not allow the user to select the deployment in the launch configuration
> > > dialog that does not have an artifact-location pair:
> > > 
> > > org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment)
> > > 
> > > Consider relaxing this constraint in the UI.
> > 
> > Covered in defect 236308.
> 
> Ignore (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=236308#c3).

As such, we should be more clear in the deployment documentation that at least one artifact/location pair is required and the artifact must contain all of the test assets required for test execution.

Comment 5 Paul Slauenwhite

2010-05-20 07:55:11 EDT

No longer required.

Comment 6 Paul Slauenwhite

2010-05-20 09:58:59 EDT

Closing.