Understanding How UFT Merges Test Object Configuration Files

Each time you open UFT, it reads all of the test object configuration files located in the <UFT installation folder>\dat\Extensibility\<UFT add-in name> folders. UFT then merges the information for each test object class from the different files into a single test object class definition, according to the priority of each test object configuration file.

UFT ignores the definitions in a test object configuration file in the following situations:

Define the priority of each test object configuration file using the Priority attribute of the TypeInformation element.

If the priority of a test object configuration file is higher than the existing class definitions, it overrides any existing test object class definitions, including built-in UFT information. For this reason, be aware of any built-in functionality that will be overridden before you change the priority of a test object configuration file.

When multiple test object class definitions exist, UFT must handle any conflicts that arise. The following sections describe the process UFT follows when ClassInfo, ListOfValues, and Operation elements are defined in multiple test object configuration files. All of the IdentificationProperty elements for a specific test object class must be defined in only one test object configuration file.

For more information, see the Micro Focus UFT Test Object Schema Help (available with the Java Add-in Extensibility SDK Help).