The Test Object Configuration XML File

The first stage of developing support for a custom toolkit is to define the test object classes that you want UFT to use to represent your application controls. You define the test object classes in a 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.

To ensure the structural correctness of your test object configuration file, you can validate it against the ClassesDefintions.xsd file. This file is installed with UFT, in the <UFT installation folder>\dat folder . (For backward compatibility reasons, UFT still supports certain XML structures that do not pass validation against this XSD.)

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

For details on the syntax and structure of a test object configuration file, see the Unified Functional Testing Test Object Schema Help.