Comparing and Merging Object Repositories

Relevant for: GUI tests and components

When working with object repositories, you may need to compare object repositories to see differences or merge multiple object repositories to simplify your testing assets.

To assist with this UFT provides tools to help you compare and merge object repositories.

Object Repository Comparison tool

The Object Repository Comparison Tool enables you to compare two shared object repositories, and view the differences in their objects, such as different object names, different test object descriptions, and so on. The tool is accessible from the Object Repository Manager.

Differences between objects in the two object repository files are identified according to default rules. During the comparison process, the object repository files remain unchanged.

After the comparison process, the Comparison Tool provides a graphic presentation of the objects in the object repositories, which are shown as nodes in a hierarchy. Objects that have differences, as well as unique objects that are included in one object repository only, can be identified according to a color configuration that you can specify. Objects that are included in one object repository only are indicated in the other object repository by the text "Does not exist". You can also view the properties and values of each object that you select in either object repository.

The Object Repository Comparison Tool is designed for comparing repositories that are different, but have a set of overlapping objects. This tool is useful if you want to decide whether to merge two repositories without performing the actual merge and addressing object conflicts in the Object Repository Merge Tool.

Back to top

Object Repository Merge tool

UFT enables you to merge two shared object repositories into a single shared object repository using the Object Repository Merge Tool.

This tool also enables you to merge objects from the local object repository of one or more actions or components into a shared object repository. For example, if UFT learned objects locally in a specific action in your test or in a component, you may want to add the objects to the shared object repository, so that they are available to all actions (even in different tests) or components that use that object repository.

When you have multiple shared object repositories that contain test objects from the same area of your application, it may be useful to combine those test objects into a single object repository for easier maintenance. You could do this by manually moving or copying objects in the Object Repository Manager. However, if you have test objects in different object repositories that represent the same object in your application, and the descriptions for these objects in the different object repositories are not identical, it may be difficult to recognize and handle these conflicts.

The Object Repository Merge Tool helps you to solve the above problem by merging two selected object repositories for you, and providing options for addressing test objects with conflicting descriptions. Using this tool, you merge two shared object repositories (called the primary object repository and the secondary object repository), into a new, third object repository, called the target object repository. Objects in the primary and secondary object repositories are automatically compared, and then added to the target object repository according to configurable rules that define the defaults for how conflicts between objects are resolved.

Back to top

See also: