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

Bug 142484

Summary: [Usability] Workbench location portability
Product: z_Archived Reporter: Julien Canches <julien.canches>
Component: TPTPAssignee: Paul Slauenwhite <paulslau>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: paulslau
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: closed471

Description Julien Canches CLA 2006-05-18 09:02:49 EDT 
The purpose of this bugzilla is to improve the ability to run the same JUnit plug-in test on various workspaces.
Currently, the only way to ensure that a JUnit plug-in test can be run on two different machines (with different OS, installation directories, languages, etc.) is to use the "default deployment" in the test launch configuration. This ensures that appropriate options will be chosen, depending on the machine specifics.
If one creates a workbench location, this location will contain fixed values, such as directories, VM args, and so on. For each option that the workbench location editor provides, it should be possible to choose an "automatic" value. The involved options are:
- workbench location
- program arguments
- VM arguments
Comment 1 Paul Slauenwhite CLA 2007-01-16 10:26:10 EST 
Reassigning to the component leads to triage for 4.4.
Comment 2 Paul Slauenwhite CLA 2007-01-26 08:25:19 EST 
Targeting to future since not containable in 4.4.
Comment 3 Paul Slauenwhite CLA 2007-01-26 09:01:31 EST 
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision.
Comment 4 Paul Slauenwhite CLA 2007-01-26 09:03:57 EST 
Correction:  The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Comment 5 Paul Slauenwhite CLA 2009-06-09 14:47:53 EDT 

*** This bug has been marked as a duplicate of bug 195846 ***
Comment 6 Kathy Chan CLA 2010-11-18 18:50:44 EST 
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.