Script Extensions that require Name Mapping files
Updating a script extension and then seeing those changes across all projects and test suites is easy. I've incorporated objects that require Name Mapping inside my script extension. So an...
Hi Levi,
As far as I can see, you've contacted the TestComplete Support team. Here is their reply:
You can simply share a NameMapping project item with several projects (even if they belong to different project suites). Please see the "Sharing Project Items and Their Child Elements Among Several Projects" help topic (http://support.smartbear.com/viewarticle/32430/). So, it will allow you to have only one NameMapping file stored in a shared folder for all your projects.
But, please note that the situation when you use NameMapping in script extensions isn't typical. Script extensions are convenient for the creation of utility functions which can be used in different projects, but NameMapping, as you mentioned, makes these functions dependent, and in every project you will need to think about providing the needed condition for their work. Since every object in TestComplete can be addressed by its full name, you can make your script extension more reliable by avoiding using Name Mapping.
The following help topics can be useful:
"Default Object Naming" -- http://support.smartbear.com/viewarticle/28459/
"Find Method" (and topics from the "See also" section) -- http://support.smartbear.com/viewarticle/30995/
