Community
Participate
Working Groups
Simplify the Test Launch Configuration dialogs. This feature is necessary if improvements to deployments/locations and the Eclipse Launch Configurations are made.
Themes: Simple to Use
I'm assigning this to Dominique, since his team owns the test launch configuration code. Wayne, can you please elaborate on the kind of simplification you're envisioning? Dominique's team may want your collaboration in writing the design doc for this feature.
The purpose of this enhancement is to provide some user experience enhancements for running tests. It is related to Bug 74917 (Simplify deployment, locations management). While there were a number of improvements in this area for the localhost scenarios for 4.0, the enhancement has been re-opened to consider addressing remote use cases as well. As a result, this enhancment work may include updating the Test Launch Configuration UI to simply enter in a hostname or perhaps to allow users to create a deployment or any other pre-requisite resource without having to leave the Launch Configuration UI completely (i.e., allow users to launch the new wizards from the Launch Config dialog). But the detailed design is dependant on the final solution for 74917. Enhancement 83786 is also intended to cover any changes required if Eclipse is able to make improvements to the Launch Configurations (e.g., Bug 74480).
Feature Description document available at http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_83786.html
[sizing = 3 weeks]
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
Changing target as per the official 4.1 enhancement plan.
Upgrading suggested priority.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Reassign 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).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
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 the originator of this enhancement/defect has an inactive Bugzilla account 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.
