Community
Participate
Working Groups
For some types of testers, the concept and requirement of deployments and locations or other artifacts (e.g., to run a test) is particularly difficult. Users do not realize they must manually create deployments, locations, etc. (or generate the resources) in order to run a test even on the local machine. Consider simplifying how deploying or running a test / test suite is done. For some types of users (e.g., performance testers) they are not interested in creating Eclipse or Hyades resources in order to deploy/run a test. They simply want to select the test to run, choose where to run it (e.g., locally or on a remote host) and then just run it. If it is possible to remove the requirement for users to create and manage deployment resources (i.e., do that for the user under-the-covers), that would be a great user experience improvement.
The use case to run a test on localhost by defaul when there is no deployment specified gives the user the conveniency with a simplest senario to execute a test. However, to run a test on a remote host is not a default behavior. The purpose of deployment is just to handle cases like this, it manages: groups of test assets(through Artifact), multiple destinations(through Location) and the mappings of test assets and destinations(through Artifact-Location Pairs) which makes a very flexible deployment possible. Talked with Joe and Julien. Bianca to provide a function to create a default deployment at runtime and check in. Then pass on to Julien for necessary changes in Launch Configuration and maybe Test Navigator.
Adding David to the CC as this effects RPT.
Added static method createDefaultDeployment() in class org.eclipse.hyades.models.common.configuration.util.ConfigurationUtil to provide a new default deployment for "localhost". Julien, I suppose this deployment will only be used "behind-the-scene" and won't be exposed through UI since it's just created in memory and does not exist on disk, right?
Modified the configuration facades (DeploymentLaunchConfigurationFacade and parent class) which are now able to handle "default deployment" (ie. volatile EMF object not persisted to a resource). Modified the DefaultDeploymentsProvider which now always adds the "default deployment" to the list proposed in the Launch Configuration dialog. Contributors need to override this provider using the "DeploymentsProvider" extension point if they don't want to show this default deployment for their tests. Also changed Bianca's implementation of createDefaultDeployment() so that it always return the same object (this makes deployments's comparisons much more simpler).
This bugzilla also maps to a TPTP feature which actually is a larger enhancement to simplify the overall concept of deployments and locations within TPTP. While I believe the fixes described above help improve the issue for running tests on the localhost, the initial intention of this enhancement was to further simplify how deployments and locations are surfaced to the user overall. Currently the TPTP feature list has this feature and target it for 4.0. I think it would be appropriate to re-open this bugzilla as it maps to this important feature for TPTP 4.0.
As I described in my previous comment, I feel the fixes do not fully address the enhancement to simplify deployment, locations, artificats management and creation as was the initial intent of the enhancement. While the current fix helps with the localhost case, ideally I would like to see a simplfication of locations, deployments, and artifacts. Users should not have to manage the creation of these separate objects/items. For example, it should be possible to allow users to execute tests (local or otherwise) without having to first create the items. The required items could perhaps be created under-the-covers, with minimal user intervention (where possible).
Moving the bugzilla to TPTP project as it was reopened for future version.
Setting version to 4.1 so it can be considered by the requirements team for 4.1.
The Launch Configurations enhancements will be separately addressed in bugzilla 83786. Reassigning to Bianca.
[sizing = 5 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
Reassigning to current component owner.
Correcting version for this enhancement (defaulting to the current release). See http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html for more information.
Correction: Future is a valid version for this enhancement based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html. As such, the implicit assumption is that is enhancement is of a lower priority. If incorrect, the originator should correct the version.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
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 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.
