Deploying the Custom Toolkit Support (Version 2021 R1 or earlier)

Relevant for version 2021 R1 or earlier

This topic describes how to deploy the toolkit support for the version 2021 R1 or earlier. For version 2022 or later, see Deploying the Custom Toolkit Support (Version 2022 or later).

To deploy the toolkit support set that you create, you must place the files in specific locations within the OpenText Functional Testing installation folder.

Recommended File Locations

Before you begin, create a folder with the name of your custom toolkit in the <OpenText Functional Testing installdir>\dat\Extensibility\WPF folder, if one does not already exist.

The following table describes the appropriate location for each of the toolkit support files:

File Name

Location

<Custom Toolkit Name>TestObjects.xml

Note: This is the recommended file name convention. You can have more than one test object configuration XML file, and name them as you wish.

When deploying support for WPF:

  • <OpenText Functional Testing installdir>\dat\Extensibility\WPF

  • <OpenText_Functional_Testing_Add-in_for_ALM_installdir>\dat\Extensibility\WPF

    (Optional. Required only if the folder exists, which means the OpenText Functional Testing Add-in for ALM was installed independently from the ALM Add-ins page and not as part of the OpenText Functional Testing installation.)

When deploying support for Silverlight:

  • <OpenText Functional Testing installdir>\dat\
    Extensibility\Slv

  • <OpenText_Functional_Testing_Add-in_for_ALM_installdir>\dat\Extensibility\Slv

    (Optional. Required only if the folder exists, which means the OpenText Functional Testing Add-in for ALM was installed independently from the ALM Add-ins page and not as part of the OpenText Functional Testing installation.)

<Custom Toolkit Name>.cfg

When deploying support for WPF:

<OpenText Functional Testing installdir>\dat\Extensibility\WPF\<custom toolkit name>

When deploying support for Silverlight:

<OpenText Functional Testing installdir>\dat\Extensibility\Slv\<custom toolkit name>

Custom Server DLL

The .dll file can be located on the computer on which OpenText Functional Testing is installed, or in an accessible network location.

Specify the location in the DllName element in <Custom Toolkit Name>.cfg

Icon files for new test object classes (optional)

The file can be a .dll, .exe, or .ico file, located on the computer on which OpenText Functional Testing is installed, or in an accessible network location.

Specify the location in <Custom Toolkit Name>TestObjects.xml

Help files for the test object classes (optional)

Must be a .chm file, located on the computer on which OpenText Functional Testing is installed.

Specify the location in <Custom Toolkit Name>TestObjects.xml

You specify the locations of the custom server DLL, Help, and icon files in the toolkit support set's configuration files. You can specify these locations using relative paths. For more information, see the Test Object Schema Help and the Toolkit Configuration Schema Help.

The recommended locations for these files are described in the following table:

File Name

Location

Custom Server DLL files

When deploying support for WPF:

<OpenText Functional Testing installdir>\dat\Extensibility\WPF\<custom toolkit name>\CustomServers

When deploying support for Silverlight:

<OpenText Functional Testing installdir>\dat\Extensibility\Slv\<custom toolkit name>\CustomServers

Icon files

When deploying support for WPF:

<OpenText Functional Testing installdir>\dat\Extensibility\WPF\<custom toolkit name>\Res

When deploying support for Silverlight:

<OpenText Functional Testing installdir>\dat\Extensibility\Slv\<custom toolkit name>\Res

Help files

When deploying support for WPF:

<OpenText Functional Testing installdir>\dat\Extensibility\WPF\<custom toolkit name>\Help

When deploying support for Silverlight:

<OpenText Functional Testing installdir>\dat\Extensibility\Slv\<custom toolkit name>\Help

Back to top

Setting the DevelopmentMode Attribute

If you modify attributes of Identification Property elements in the test object configuration file, keep the DevelopmentMode attribute of the TypeInformation element set to true during the design stages of the custom toolkit support. Before you deploy the custom toolkit support set for regular use, be sure to remove this attribute (or set it to false). For more information, see Modifying Identification Property Attributes in a Test Object Configuration File.

Back to top