NameMapping vs Objects Defined In Code
Is there any benefit to using the Namemapping feature in TC as opposed to referencing the object locations in code? Currently, I have functions that will give me certain parts of the application,...
Forum Discussion
The beauty about NameMapping is that, if a component changes, you simply edit the identification criteria in your NameMapping repository and all the objects then reference off that. There's no need to update any references to the object.
For example, let's say I have something like Aliases.MyApp.MyForm which has child objects of MyOKButton, MyCancelButton, MyTextEdit, and MyToolBar. Some developer decides to change MyForm to a different class or change the caption or something. My code has 40-11 zillion references to MyForm and various calls to the child objects.
With NameMapping, all I need to do is edit the repository information for MyForm. So long as the child objects are still child objects of MyForm, everything should then just translate. I don't need to make any code changes in any of my tests, I don't need to change any of my references to those child objects, everything just "works".