Understanding the Test Object Configuration File

The first stage of developing support for a custom toolkit is to introduce the test object model that you want UFT to use to test your applications and controls. To do this, you define the test object model in the test object configuration XML file. You need to create a test object class for every type of custom control for which you want to extend or modify UFT support.

In a test object configuration XML, you define the test object classes (for example, the test object methods they support, their identification properties, and so on).

You create a ClassInfo element for each test object class that you want to define. In addition, you define the name of the environment or custom toolkit for which the test object classes are intended (in the PackageName attribute of the TypeInformation element), and the UFT add-in which these test object classes extend (in the AddinName attribute of the TypeInformation element).

If the relevant add-in is not loaded when UFT opens, UFT does not load the information in this XML. Similarly, if the name of the environment or custom toolkit is displayed in the Add-in Manager dialog box and its check box is not selected, the information in this XML is not loaded.

For more information, see How UFT Loads the Test Object Configuration XML.

The sections below describe the information that you can include in a test object class definition.

For information on the structure and syntax of a test object configuration XML, see UFT Test Object Schema Help.

See also: