Open topic with navigation
Custom Web Control or Custom Control. An HTML element in a Web application that, together with its sub-elements, provides a distinct logical functionality or set of functionalities and properties. A custom control can contain other controls. Whether to handle a control individually or to view it as part of an aggregate control is a design issue to be decided when creating the toolkit.
For example, a DIV element that contains a text box, an OK button and a Cancel button might be a custom control.
Root element. The top-level, or containing element of a control. In the example above, the DIV element is the root element.
Test Object Class. A class within UFT that represents controls having a common set of functionalities and properties. A test object class defines a number of characteristics, including the events to which the test objects of the class will respond during test recording, the naming of individual test objects, the operations that can be used with the test objects, and the identification properties. For identification properties, the class defines:
Some of these classes are built-in to UFT and some are provided by an add-in or custom toolkit support set.
Test Object. An instance of a test object class within UFT that represents a single control instance in the application. When UFT learns an application, it creates a test object for each application control. If the application control can be identified as belonging to a test object class, a test object of that class is created. If not, a generic test object for the relevant environment is created. For example, in Web applications, the generic object is WebElement.
Toolkit. A set of controls.
Toolkit Support Set. A set of files you create that instructs UFT on how to create test objects for the controls in a toolkit, how to record events on those controls, and how to execute operations on the controls during test run.