Community
Participate
Working Groups
Using 4.5-200806070100 build Steps to reproduce: 1. Create a plugin project 2. Create a TPTP JUnit-Plugin test(jplugin) 3. Popualte the test, create some cases and add invocations in behaviour tab 4. Modify test case methods in java file 5. Create an Artifact(art) associate with that JUnit-plugin test 6. Create a location(loc), a workbench location(wkloc), a deployment(dep) 7. Add art,loc,wkloc in dep , make art+loc and art+wkloc (2 pairs)--save 8. right click on jplugin--Run As--Run configuration, create a new configuration under Test, we can find dep is not in the deployment window(that's work as design) 9. remove art+loc pair in dep--save and go to run configuration again--dep appears 10. add art+loc pair again in dep--in run configuration, dep still exists, it should have the same result as step 8. 11. if we go on working with step 10, run jplugin test with dep, NPE will raise.
problem exists in TPTP-4.6.0-200906191311
Also (from defect 289521): The current design allows tests to be executed with deployments without an artifact-location pair or artifact when using ASF. However, the UI does not allow the user to select the deployment in the launch configuration dialog that does not have an artifact-location pair: org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment) Consider relaxing this constraint in the UI.
(In reply to comment #2) > Also (from defect 289521): > > The current design allows tests to be executed with deployments > without an artifact-location pair or artifact when using ASF. However, the UI > does not allow the user to select the deployment in the launch configuration > dialog that does not have an artifact-location pair: > > org.eclipse.hyades.test.core.internal.launch.extensions.DefaultDeploymentsProvider.isDeploymentApplicable(TPFDeployment) > > Consider relaxing this constraint in the UI. After testing ASF with deployments without an artifact-location pair, without an artifact, or with an artifact with no associated test assets, the deployment/location is ignored and the test is executed using the default deployment (for example, localhost). As such, we should not relax this constraint in the UI.
Deferring to TPTP 4.7.0.
No longer required by a consuming product.
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.
