Open topic with navigation
In the test object configuration file you defined the identification properties for your test object classes. When UFT runs a test it needs to retrieve the values for these properties. UFT uses identification property run-time values in different test object methods, such as GetROProperty. Identification property run-time values are also required for different basic capabilities, such as creating checkpoints and outputting values.
This function must return the property value in one of the following formats: String, Integer, Boolean, or array. When returning an array, use the toSafeArray function to convert the array to the format that UFT expects. When you provide an identification property value in an array format, UFT converts the array to a semicolon-delimited string.
UFT uses the base test object class implementation to retrieve the identification property values when the following conditions are met:
The control includes a base element (for more information, see Extending an Existing Test Object Class).
The identification property is defined in the test object configuration file with the same name as a base test object class property.
You do not provide a function that returns a value for that identification property.
Base test object class implementation for retrieving the value for this identification property value is not available.
The base test object class implementation does not meet your needs.
By designing the function that returns identification property values to return a value for the logical_name property, you can control how UFT names test objects of this test object class. For more information, see Customizing the Test Object Name.
After you create support for retrieving the run-time values of identification properties, you can test that your toolkit support set correctly enables UFT to run checkpoints on your Web elements, output property values, display the property values in the Object Spy, and run test steps with the GetROProperty operation. For more information on testing your toolkit support set, see Testing the Toolkit Support Set During Development.