1. In Microsoft Visual Studio, select File > New> Project.

2. Enter UFT in the search box and select the UFT WPF CustomServer or UFT Silverlight CustomServer template.

3. Provide a name and location for your new project, and a name for the solution (or accept the default values provided).

4. Click OK. The WPF or Silverlight Custom Server Setup dialog box opens, depending on the template you selected.

   The project name is also used as the default value for some of the fields in the dialog box.

To successfully create a project using the UFT Silverlight CustomServer template, you must have the Microsoft Silverlight Tools for Visual Studio installed.

How to create support for a Custom Toolkit (Version 2021 R1 or earlier)

• Developing Support for a Custom WPF/Silverlight Toolkit (Version 2021 or earlier)

• Custom Servers (Version 2021 R1 or earlier)

• Custom Support API Reference

• Toolkit Configuration Schema Help

• Test Object Schema

The name of the custom server class to create in the new project.

Indicates that you want to design or override implementation for running test object operations on the control.

If you select this option, the Run interface that you specify is defined and tagged with the RunInterfaceAttribute. In the custom server class, the interface is implemented with a method stub for an example test object operation. The example test object operation is also added to the project's test object configuration file.

The name of the interface in which you want to implement support for the test object operations.

Available only when Customize running operations is selected.

Indicates that you want to design support for recording test object operations on the control.

If you select this option, the custom server class is defined to implement the IRecord interface and includes method stubs for the interface's methods.

Indicates that you want to design or override implementation for retrieving identification property values from the control.

If you select this option, the Property interface that you specify is defined and tagged with the CustomPropInterfaceAttribute. In the custom server class, the interface is implemented with a method stub for an example identification property. The example identification property is also added to the project's test object configuration file.

The name of the interface in which you want to implement support for property value retrieval.

Available only when Customize property retrieval is selected.

Indicates that you want OpenText Functional Testing to treat some of the custom control's child objects as an integral part of the control and not as independent objects.

If you select this option, a preliminary implementation of the IsKnownPartOf method in the IComponentDetector interface is created in the custom server class. Implement the method to return true for the relevant child objects.

Indicates that you want the standard checkpoints and output values that OpenText Functional Testing creates on your test object to be table checkpoints and output values.

If you select this option, a preliminary implementation of the ItableVerify interface is created in the custom server class. Implement this interface according to your needs.

A name for the environment, or set of controls, that you want to support with this toolkit support set.

You may want the name to indicate whether this is a WPF or Silverlight toolkit. After you deploy your support, OpenText Functional Testing displays this name in the Add-in Manager as a child node under the WPF add-in node, enabling the user to specify whether to load support for this environment.

In the new project created, the toolkit name is used to create the configuration file names, and entered in the PackageName attribute of the TypeInformation element in the test object configuration file (if you select Auto generate the XML configuration files). It is also used for the root namespace of the project.

Indicates that in the new project created, a toolkit configuration file and test object configuration file should also be created. The files are created with basic definitions, according to the details you specify in this dialog box.

In a toolkit support set, the definitions for all of the controls that you want to support are included in one toolkit configuration file, and one test object configuration file. On the other hand, you design a separate custom server for each control you support. Therefore, if you use the template to create additional custom servers, you might not want to generate additional XML files. Alternatively, you can decide to generate the XML configuration files as well, and then copy the information from these new files to your main configuration files.

The name of the custom control type for which you want to develop support.

For Silverlight: A full type name, including namespaces.

For WPF: This can be one of the following:

• A full type name, including namespaces. For example: Infragistics.Controls.Editors.XamComboEditor

• A full type name and an assembly name. For example: Infragistics.Controls.Editors.XamComboEditor, InfragisticsWPF4.Controls.Editors.XamComboEditor.v12.1

• An assembly qualified name. For example: Infragistics.Controls.Editors.XamComboEditor, InfragisticsWPF4.Controls.Editors.XamComboEditor.v12.1, Version=12.1.20121.1010, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb

The test object class that you want OpenText Functional Testing to use to represent the custom control.

In the new project created, a basic definition for this new test object class is created in the test object configuration file (if you select Auto generate the XML configuration files).

The test object class that your new test object class extends.

Select from the list of built in OpenText Functional Testing test object classes, or enter a name of a test object class that you defined in a WPF or Silverlight Add-in Extensibility test object configuration file. (WPF test object classes need to extend other WPF test object classes, and Silverlight test object classes need to extend other Silverlight test object classes.)

Default: WpfObject or SlvObject