Local copies of objects in shared object repositories

Relevant for: GUI tests and components

You can create a local copy of any object stored in a shared object repository that is associated with the action or component currently displayed in the in the object repository tree.

Copying an object to the local repository is useful, for example, if you want to modify an object in the current action or component, without affecting other actions or components that use the shared object repository.

When you create a local copy of an object and modify it in the Object Repository window, the changes you make affect only the action or component in which you make the change. Conversely, if you modify the object in the shared object repository using the Object Repository Manager, the changes you make are reflected in all actions or components that use the shared object repository. However, if you modify an object in a shared object repository, and a copy of the object (with the same name) exists in the local repository, your changes do not affect the local copy of the object in your action or component.

During a run session, UFT uses the test object in the local object repository to identify the object in your application. This is because the local object repository has higher priority than any shared object repository associated with the action or component.

If you copy an object to the local object repository, its parent objects are also copied to the local object repository. However, you cannot copy an object to the local object repository if an object or its parent objects use unmapped repository parameters.

If an object or its parent objects are parameterized using repository parameters, the repository parameter values are converted when you copy the object to the local object repository. If the value is a constant value, the property receives the same constant value.