| Summary: | [Functionality, Usability] Problems with Test Navigator, proxies, and renaming | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mark A. Sibert <sibert> |
| Component: | TPTP | Assignee: | Jerome Gout <jerome.gout> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 83087 | ||
|
Description
Mark A. Sibert
Try to reproduce using a recent RPT 7.0 build (20060131_111). Create a Http performance test in a folder. Try to open the test -> Editor opens normally. Close the test editor. Rename the folder -> the new folder appears (selected and collapsed). Double click on the test node to open -> Editor opens normally. As far as test rename is concerned, downstream products are able to control the renaming of their test assets by using the IProxyNodeRenamer interface. If an element (which should be a proxy node in the test navigator) has inter-asset references, the proxy node renaming framework allows to propagate the change of the element name through all dependencies. IProxyNodeRenamer.performRename(String newName) The default implementation of this interface for TPTP proxy nodes is mainly done in CMNNamedElementProxyNode. In that class the performRename method only rename the EMF object name. One can imagine a much more complex treatment for specific proxy nodes. ACTION: Please verify/close this defect. 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. |