Auto update scripts when Name Mapping items/aliases are renamed
Hi, When a Name Mapping item name is changed, it would be great to have all related NameMapping, Aliases updated accordingly through out the code. For example: A Name Mapping Aliases.MainWindows.NavigationWindow.OkButton is renamed to Aliases.MainWindows.NavigationPanel.OkButton would update all references of the old Aliases path to the new one. Thanks Simoin GletProvide Ability to Clean Alias and Mapped Objects Not Used in Tests
In our trial and error approach to learning TC we have found ourselves with excessbaggage (unused mapped objects and Aliases) which we wish to clean up. At some point we disabled 'Map object names automatically' and have a mix of testsusing Mapped and Aliased object. The ability to removed mapped objects and aliases which are used in keyword and script tests would be highly benificial. Hereisa thread which discusses in further detail. Thanks for your consideration.Make Name Mapping mergeable
Hi, A Name Mapping file is an xml file but its content is difficult to understand and impossible to merge. The current structure forces teams working on the same project to dedicate one personne only to edit the Name Mapping file. Once the editing is done, other members of the project must overwrite their local file. The must be a better way to keep the Name Mapping file in synch. Thanks Simon Glet
Find Usages of Name Mapping Objects / Aliases
In order to be able to effectively maintain the Name Mapping & Aliases it would be useful to be able to right click an object in the Name Mapping/Aliases hierarchy and 'Find Usages' which will then bring up a dialog to show all Scripts & Keyword test files that contain references to that object. You can then double click the file in the dialog to take you to the first reference in the file.
Support references to NameMappings of other projects
We are dealing with many different executables, which are interacting with each other in our tests. What we would like is to do is to have distinct responsible persons to maintain the NameMapping and the tests for each of the individual applications. In the "main" test project, we like to reference the "subprojects" and plug them together to obtain the integration test suite. This is working fine for script files (where you can add a reference to an "external" file, which is part of another project). But this does not work for the NameMapping file. It is only possible to have one monolithic NameMapping file in the main project. The only way at the moment is to "merge" all the NameMappings of the subprojects to the main project's NameMapping, which is error prone and cumbersome. It would be great if the NameMapping of the main project could somehow "include" or "reference" other NameMapping files from other projects, which are part of the project suite.Ability to show link between Aliases and Name Mapping objects
It would be useful to be able to show the link between an Alias object and an object in the Name Mapping. As time has gone on my Name Mapping has need to be updatedas objectshierarchies have changed in my tested application, however, in order to prevent me from having to update all of my scripts and keyword tests I have left the Aliases in their original structure. It has now become difficult to identify which Alias objects relate to which Name Mapping objects.
