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

Bug 87414

Summary:	Dynamic test asset deployment when test closure is not staticly definable
Product:	z_Archived	Reporter:	Bill Tobin <wctobin>
Component:	TPTP	Assignee:	Joe Toomey <jptoomey>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P1	CC:	jptoomey
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
URL:	http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_87414.html
Whiteboard:
Deadline:	2006-02-10

Description Bill Tobin

2005-03-08 13:33:07 EST

It is not always possible to statically determine the closure of a test.  For 
instance if a test uses reflection to dynamically bind to classes, the 
dynamically bound classes are not statically recognizable as part of the 
test.  Needed is the ability to request additional test assets get deployed 
after the original test has started execution.  This action needs to be 
(optionally?) synchronous so that execution of the test blocks until the 
additional test assets are available.

Comment 1 Frank McGrath

2005-03-16 12:22:12 EST

Tests may have dependencies on ancillary file-based assets. These too should be
dynamically accessible.  

Even when determining the closure is possible, it may cause more test assets to
be sent than are needed for a specific execution. For example, we could consider
all assets in a project and in referenced projects to be the closure.

Even when it is possible to derive a more constrained closure for a framework of
loosely coupled tests, it may be the case that a specific test execution uses a
small subset of the assets because of conditional logic that is used during the
execution.  

Regarding multiple projects - in order to support remote execution of
cross-project test execution, the remote machine will need to have the assets
isolated per project, and placed in a known or determinable location on the
remote machine.

Comment 2 Ruth Lee

2005-05-19 13:16:53 EDT

Moving the tptp.test-inbox@eclipse.org bugzillas over to the new default owner
of Test.Execution.

Comment 3 David Hodges

2005-05-19 14:21:55 EDT

Forward to Kent to consider enhancement for the execution component

Comment 4 Joe Toomey

2005-09-01 17:22:51 EDT

Mark for consideration in 4.2.

Comment 5 Christophe Telep

2005-12-09 10:21:42 EST

proposed to be plan for 4.2 (plan keyword added)

Comment 6 Christophe Telep

2005-12-09 12:19:00 EST

Target set to 4.2

Comment 7 Kent D Siefkes

2005-12-12 10:37:04 EST

Re-assigning to Joe Toomey, who plans to implement this in TPTP 4.2.

Comment 8 Joe Toomey

2006-02-27 14:03:02 EST

Service framework is functioning.  Still need to implement RemoteResourceProvider service, add doc and tests.  On track to complete in i2.

Comment 9 Joe Toomey

2006-03-07 13:49:45 EST

Preparing for presentation of this work to TPTP Test Execution team.

Comment 10 Joe Toomey

2006-03-30 15:41:20 EST

Delivered for i2.

JUnit tests checked into test-results project.  Relevant APIs are javadoc'd.

Comment 11 Paul Slauenwhite

2006-11-16 09:00:00 EST

ACTION: Please verify/close this defect.

Comment 12 Joe Toomey

2006-11-16 09:58:21 EST

Closing...