Mapping Test Object Classes to Inner Objects

Within the MicTest root element of the toolkit configuration XML file, under the Key element where Name="Test Objects", you define one Key element for each custom Delphi test object class that you want to map.

The Name attribute of this Key element must contain the name of the custom Delphi test object class. For example, the excerpt below is part of the test object configuration file that maps the DelphiTrackBar test object class to the WinObject test object class that serves as its inner object:

This section describes additional optional elements that you can define within the Key element defined for each custom Delphi test object class:

In some dialog boxes, UFT displays a list of available test object classes per environment (for example, the Define New Test Object dialog box, the Object Identification dialog box, and the Step Generator dialog box). If you want UFT to display your custom Delphi test object classes in these dialog boxes, you must add the following lines in the Key element for each custom Delphi test object class:

If you want UFT to treat your custom Delphi test object class as a grid (table), you must add additional elements within the Key element that you define for this test object class. For more information, see Instructing UFT to Treat Your Custom Grid Control as a Table . To instruct UFT to treat this type of test object as a table test object when creating checkpoints and output values.

The Checkpoint Properties dialog box in UFT includes a Checkpoint timeout value (in seconds). You can customize the default checkpoint timeout value that is used when creating new checkpoints on your custom test object class. (Otherwise the default is 0). To set the default checkpoint timeout value, add an additional Key element, like the one below, within the Key element defined for your custom Delphi test object class. Replace the number 10 in these lines with the default you want UFT to use: