This task describes how to define, implement, and debug the operations that your test object class supports.
Note: This task is part of a higher-level task. For details, see How to Create or Update Support for a Single Control.
- Define the list of operations supported by this test object class
In the Operations Tab (Test Object Class Designer), do the following:
Add or remove operations, or select base class operations to override.
Keep in mind that if the following conditions are met, you need to override all of the base class operations that are not supported by the WebElement test object class:
The control you are supporting is not represented by the type of HTML element supported by the base class.
You did not implement a get base element function that returns such an element to UFT One.
For operations that you add or override, define the method signature and optionally, additional information.
Specify the default operation for this test object class (optional).
If you do not select a default operation, the base class's default operation is used.
The information defined in this tab is stored in the toolkit support set XML files.
In this case, operations that you do not override will be available when editing tests, but will not be implemented. Including these operations in test steps will result in run-time errors. For more details, see the section on extending an existing test object class in the Micro Focus UFT One Web Add-in Extensibility Developer Guide.
How these definitions affect the files:
For more details, see When Are Your Changes Applied and Saved.