Share this page
Deploying the Custom Support Set
The next stage of extending OpenText Functional Testing GUI testing support for custom controls is deployment. This means placing all files you created in the correct locations, so that the custom support is available to OpenText Functional Testing.
After you deploy the custom support, if you run an application that contains the custom controls and perform OpenText Functional Testing operations on the application, you can see the effects of the support you designed.
Placing Files in the Correct Locations
To deploy the support set that you create, place the files in the locations described in the following table. Make sure that OpenText Functional Testing is closed before placing the files in their appropriate locations.
File Name | Location |
|---|---|
SwfConfig.xml | <OpenText Functional Testing installation path>\dat |
<Test Object Configuration File Name>.xml Note: You can have more than one test object configuration file (if any), and name them as you wish. |
|
<Control Definition File Name>.xml> Note: The Control Definition file is used when creating a Custom Server using the XML coding option. You can have more than one control definition file (one for each custom control). |
|
<Custom Server File Name>.dll Note: This type of Custom Server is used when creating a Custom Server using the .NET DLL coding option. You can have more than one custom server for each custom control. | Specify the location of your compiled Custom Servers (DLLs) in the SwfConfig.xml file. |
Modifying Deployed Support
If you modify a support set that was previously deployed to OpenText Functional Testing, the actions you must perform depend on the type of change you make, as follows:
If you modify the .NET Add-in Extensibility configuration file or a test object configuration file, you must deploy the support.
If you modify a test object configuration file, you must reopen OpenText Functional Testing and open a GUI test after deploying the support.
Removing Deployed Support
To remove support for a custom control from OpenText Functional Testing after it is deployed, you must delete the corresponding section in the SwfConfig.xml file from <OpenText Functional Testing installation path>\dat and remove the corresponding test object configuration file from <OpenText Functional Testing installation path>\dat\Extensibility\DotNet.
If you remove support for a new test object method that you added in a test object configuration file, you should remove the method definition (or the whole file, if appropriate) so that OpenText Functional Testing users do not create test steps that call that method. Modify or remove the test object configuration file in: <OpenText Functional Testing Installation Path>\Dat\Extensibility\DotNet (and <OpenText Functional Testing Add-in for ALM Installation Path>\Dat\Extensibility\DotNet if relevant).
Next steps:
