I am doing a research on automated software and the development of such.
When thinking about automated testing it is required to have references of the UI present in your software, therefore one can make use of an object repository that contains references to elements on the UI it is supposed to run the automated test on.
TestComplete tells me it has a different approach and does not make use of such object repository, but of a name-mapping repository instead.
The Name Mapping repository stores all the objects of your tested applications that your automated tests use. For each object, the Name Mapping repository has an alias (a descriptive name used in tests), the object’s position in the application’s object hierarchy, the criteria by which TestComplete identifies the object in the application uniquely, and (optionally) an image ...
... The Name Mapping repository stores object identification information separately from tests making test maintenance easier. If your application changes, you will not have to change your tests. You will only have to update the Name Mapping repository.
How exactly does this differ from a regular shared object repository?