Community
Participate
Working Groups
Build ID: M20060921-0945 Steps To Reproduce: Right click on any object in the Test Navigator and you always have a copy action. This request is dependant on 166025. More information: Bug 166025 has requested for the Copy, Rename, Move, Delete... available on test assets to be exposed via APIs so a consumer of TPTP can provide there own code to perform these actions. In my case I'm particularly concerned with FileProxyNodes in the Test Navigator. Currently there's APIs for the rename action. And I think 166025 will provide similar APIs for the other global actions. This request is for such APIs to also provide something similar to the isApplicableFor() method of the IProxyNodeRenamer interface. That way it's up to the framework consumers as to whether these actions are applicable for there contributed ProxyNodes. Also, I noticed that in the case of Rename when you say it's not applicable it gets removed from the context menu for that ProxyNode. But you can still perform the rename action from the workbench's file menu. This seems inconsistent. I was expecting the TestNavigator would also set the global action handler of the sites action bar to null causing the menu to be disabled.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Jerome, will these APIs be included under 166025?
they won't be in this patch, i lacked time to introduce such mecanism
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).
Resolving as no plan to fix seems ok for our product. Will reopen if needed based on customer demand.