Open topic with navigation
From the UFT user's perspective, after you deploy the toolkit support set on a computer on which UFT is installed, the toolkit support set can be used as a UFT add-in.
When UFT opens, it displays the custom toolkit name in the Add-in Manager, as a child node under the Java Add-in node. Select the check box for your custom toolkit to instruct UFT to load support for the toolkit using the toolkit support set that you developed.
Note: Only applications that are opened after loading or unloading support for the custom toolkit are affected.
If you do not load the support for your custom toolkit, the code that you designed in your toolkit support set does not run.
If you load support for your custom toolkit:
UFT recognizes the controls in your custom toolkit and can run test steps on them.
UFT displays the name of your custom toolkit in the Environment list in all of the dialog boxes that display lists of add-ins or supported environments.
UFT displays the list of test object classes defined by your toolkit support set in dialog boxes that display the list of test object classes available for each add-in or environment. (For example: Define New Test Object dialog box, Object Identification dialog box.)
Note: Test object classes defined in a toolkit support set that was developed using a Java Add-in Extensibility SDK version earlier than 10.00 are displayed in the UFT dialog boxes as Java test object classes. To cause UFT to display these test object classes under the correct environment name, change the PackageName attribute in the test object configuration file to the name of the custom toolkit, as it appears in the Add-in Manager. Additionally, if an index identification property is implemented for any test object classes in the toolkit support set, remove this implementation to enable the use of the Generate Scripts button in the Object Identification dialog box.