Community
Participate
Working Groups
Currently the user cannot specify a workspace that they can use for the workbench that is used as the context for running test cases. The user can't also specify the plug-ins that they wish to include in the workbench. An extra page specific to the auto GUI test suite should be included in the launch configuration dialog to allow the user to specify a workspace and the plug-ins that they wish to include in the launched workbench.
Changing the version to 4.2 and the milestone to unspecified. Leaving it up to PMC to include this in the plan.
Increasing to priority 2 because it's an expected feature. Instead of using a new launch configuration page, the workbench location resource used by the Junit plugin should be used (to encourage consistency between test tools)
Created attachment 29254 [details] Patches the AutoGUIExecObjAdapter to respect settings from the hyades .location view A simple hookup of information from the TPFDeployment into the jvm args used to launch a remote eclipse for AutoGUI testing. Some hardcoded strings should be replaced with definitions from the appropriate plugins, but I couldn't find the correct plugin/Java files.
Description document: http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_109880.html
Hi Ali, For the launch configuration work, the extension point org.eclipse.hyades.test.core.launchconfigDeploymentProvider should help to do what you need. You may also vote for bug 83786, which provides some enhancements to the test launch configuration (including easier means of specifying a location for tests that just require one location).
Thanks for your comments Julien. I would have voted for the feature if I had not used up all my votes.
Setting target to future (not part of the official plan)
It would also be good to be able to define desired Eclipse startup options. In our plugins we use startup options for things such as defining specific logging levels, switching performance timings on/off, etc.
helpwanted for 4.3
Updating version/target based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Reassigning to current component lead.
Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).
In TPTP 4.5, the AGR was moved from a Technology Preview component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists) or commitment to triage or resolve opened defects. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix.
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
