Custom toolkit support sets

To extend the UFT One Web Add-in to support custom web toolkits, you create custom toolkit support sets and deploy them to UFT One. The toolkit support set is comprised of XML configuration files and JavaScript functions.

The XML configuration files define the test object classes that you create to support the custom Web controls and map them to the controls. In addition, they define how UFT One operates on the custom controls. The JavaScript functions provide an interface between UFT One and the application being tested, retrieving information about the control and performing operations on it.

In Extensibility Accelerator, when you create an extensibility project, the project contains the mandatory files for a toolkit support set. A project can contain the following types of files:

  • XML files.Extensibility Accelerator provides designers (such as the test object class designer) to guide and assist you in editing information stored in the test object configuration and toolkit configuration XML files.

  • JavaScript files. For each test object class that you create, Extensibility Accelerator creates a corresponding JavaScript file. Within the file, Extensibility Accelerator creates function stubs for the functions that you have to implement. You can jump to these files from Extensibility Accelerator to add the code necessary for implementing these functions.

  • Additional files.Extensibility Accelerator provides Import buttons, within some of the designers, to add additional files to the project.

For task details, see Create or update support for a custom toolkit.

  • A test object configuration XML file. This file describes the test object classes that you create to support the custom controls, and the identification properties and test object operations that need to be supported for those test objects.

    For details on the structure and syntax of this XML, see the UFT One Test Object Schema Help.

  • A toolkit configuration XML file. This file maps the test object classes that you create to the relevant controls, and provides implementation details for how UFT One operates on the control. Some implementation details are contained in this configuration file, others are in JavaScript files that this file references.

    For details on the structure and syntax of this XML, see the Toolkit Configuration Schema Help, available in the Extensibility Accelerator Help.

  • JavaScript files. These files contain the implementation functions referenced from the toolkit configuration XML file. UFT One calls these functions to retrieve information from or perform operations on the custom controls.

    For details, see the section on designing JavaScript functions for your toolkit support set in the Micro Focus UFT One  Web Add-in Extensibility Developer Guide.

  • Icon and Help files (Optional).

    The icon files contain icons used in UFT One to represent your test object classes. (Supported file types: .ico, .exe, .dll)

    The Help files are used for context-sensitive Help for your test object classes and their methods and properties. (Supported file type: .chm)

For details on the structure of an extensibility project, see Project Explorer.

For details on the structure of a toolkit support set deployed to UFT One, see Deployment file structure.