Understanding and Resolving Object Conflicts in QTP
After we merge two object repositories, the Object Repository Merge Tool displays the Statistics dialog box, which describes the number and type of conflicts arising during the merge. Conflicts between objects in the primary and secondary object repositories are resolved automatically by the Object Repository Merge Tool according to the default resolution settings that we define before performing the merge operation.
Merging two object repositories can result in conflicts arising due to similarities between the objects they contain. There are three types of conflicts:
1) Similar Description Conflict: Two objects which have the same name and the same object hierarchy, but which have slightly different descriptions. In this conflict type, one of the objects always has a subset of the properties set of the other object.
An object in the primary object repository
and an object in the secondary object repository have the same name, and they have similar, but not identical, description properties and values. One of the objects always has a subset of the properties set of the other object. For example, an object named Button_1 in the secondary object repository has the same description properties and values as an object named Button_1 in the primary object repository, but also has additional properties and values.
Ways to resolve Similar Description Conflict:
# By keeping the object added from the primary object repository only.
# By keeping the object added from the secondary object repository only.
# By keeping the objects from both object repositories. In this case, the Object Repository Merge Tool automatically renames the object that is added from the secondary file by adding an incremental numeric suffix to the name, for example, Edit_1.
# By ignoring the object from the local object repository and keeping the object from the shared object repository (when updating a shared object repository from a local object repository).
By default, the conflict resolution settings for conflicts of this type are configured so that the target object repository takes the object that has fewer identifying properties than the object with which it conflicts.
2) Same Name Different Description Conflict: Two objects which have the same name and the same object hierarchy, but differ somehow in their description (for example, they have different properties, or the same property with different values).
Ways to resolve Same Name Different Description Conflict:
# By keeping the object added from the primary object repository only.
# By keeping the object added from the secondary object repository only.
# By keeping the objects from both object repositories. In this case, the Object Repository Merge Tool automatically renames the object that is added from the secondary file by adding an incremental numeric suffix to the name, for example, Edit_1.
# By ignoring the object from the local object repository and keeping the object from the shared object repository (when updating a shared object repository from a local object repository).
By default, the conflict resolution settings for conflicts of this type are configured so that the target object repository takes the object from both files. The object that is added from the secondary file is renamed by adding an incremental numeric suffix to the name, for example,Edit_1. For information on changing the default settings
3) Same Description Different Name Conflict: Two objects, which have identical descriptions, have the same object hierarchy, but differ in their object names. By default, the conflict resolution settings for conflicts of this type are configured so that the target object repository takes the object name from the primary source file.
Ways to resolve Same Description Different Name Conflict:
# By taking the object name from the object in the primary object repository.
# By taking the object name from the object in the secondary object repository.
# By ignoring the object from the local object repository and keeping the object from the shared object repository (when updating a shared object repository from a local object repository).
Many More Articles on HP QuickTest Professional

An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.