You cannot import WSDL files with names that are restricted by the Windows operating system.

This list includes: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9.

Workaround: Rename the WSDL file before the import.

The following WSDLs are not supported:

• WSDL version 2.0

• WSDLs containing a <appInfo> element.

• RPC Encoded WSDLs configured as Asynchronous Web services.

• WSDLs authenticated by HTTP digest on Apache servers.

When opening many tests in the same solution using one or more of the same Web services, OpenText Functional Testing may develop a memory leak.

Workaround: Move the Web service to the file system or ALM repository:

1. Import a Web service.

2. In the Toolbox pane, right-click the Web Service activity and select one of the following:

   Move to > File System Activities

   ALM Activities

For a Web service imported as a server response:

• RPC type WSDLs cannot be imported as a server response. If you attempt to update a service from an RPC encoded WSDL, it will create a duplicate entry.

• If you end the OpenText Functional Testing.exe process during the listening stage, after the binding was added, the binding will not be removed from the system.

  Workaround: Remove the binding manually using a utility such as httpcfg.exe or netsh.exe.

• When working with SSL, certificates from a file are not supported. If you move the test to another machine, the certificate will not be saved with the test.

  Workaround: Add the certificate to the local machine store before the listener starts, and remove it at the end of the listening process.

OpenText Functional Testing has the following known issues when working with WCF type Web services:

• Configuring different security settings for operations residing on the same port is not supported.

• Some of the user event handlers (such as the AfterProcessRequestSecurity, BeforeProcessResponseSecurity, OnSendRequest, and OnReceiveResponse events) will not be invoked.

• When working with Federation type scenarios that use STS (Security Token Service), you cannot change the SOAP version.

When testing Web Services that require message-level security, the Web Service security scenario only supports SOAP version 1.1.

For SOAP 1.2 use a WCF type scenario.

OpenText Functional Testing has the following known issues when working with SAML security tokens:

• When using a SAML security token for Web services security, user-provided content may contain creation and expiration timestamps.

  To extend the life of the test, we recommend that you hard-code an expiration date in the distant future. In this is not possible, change the timestamp by implementing the OnBeforeApplyProtocolSettings event.

• When using a SAML security token for Web services security, if you edit the values in Grid mode, they may not be updated in OpenText Functional Testing.

  Workaround: To update the values, switch to Text mode and save the test.

• Web Service steps are not supported when using a SAML token with a certificate from the file system.

  Workaround: Install the certificate to the Windows store and select the certificate from the store.

OpenText Functional Testing has the following known issues when working with SOAP 1.2:

• You can choose only UserName or X509 tokens when configuring the message level security.

• When configuring the canonicalization algorithm and the transform algorithm for the message signature, you cannot use the following format: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform.

Importing a schema to a REST, HTTP, or SOAP checkpoint may remove the links of the input properties.

If you link between input and output properties in the same REST method and then delete the input property without removing the link, the link expression still remains in the output property.

If you save the test in this state, you may be unable to reopen it.

Workaround: Delete the link explicitly either before or immediately after deleting its source property.

When defining a REST method prototype in the Add/Edit REST Service dialog box - in order to use the Trim, Ignore, or Stop test options, select the checkbox in the Validate column, in the Checkpoints pane.

OpenText Functional Testing has the following known issues when working with checkpoints and REST services:

• XPath checkpoints are not supported for HTTP and REST activities.
• When running a REST method using the Run Step command, checkpoints of dynamic property values in the method linked to other property values (input or output) are ignored.

When building JSON content and loading it in the XML Grid Model for OData and Swagger, all data types other than String are included as values in the JSON content.

If you have upgraded to OpenText Functional Testing 14.03 or higher, and are working with a test created in an earlier version of OpenText Functional Testing, you may see the Update Swagger Service options in the context menu for a local REST activity, even if you are not working with a Swagger service.

In such cases, you can ignore this option.

If the URL or source file for your REST service has had changes in operation names or relative URLs, you cannot resolve these conflicts using the Resolve Conflicts wizard.

Instead, import the source from scratch and update the step manually.

You must have Visual Studio 2012 installed on the same machine as OpenText Functional Testing to create custom activities using the Activity Wizard.

The following error may occur if you place the signature file beneath a sub-folder of the addin folder.

ServiceTest was unable to drag and drop the activity: Type 'http://hp.vtd.schemas/types/v1.0:GeneralPropertiesType' is not declared.

Workaround: Modify the relative path of the Types schema.

For example:

.schemaLocation="../../dat/schemas/Types.xsd".

If you modify the activity structure in the signature file, you will be unable to open tests using that activity.

To modify an activity structure:

1. Create a new activity with the new structure.
2. Replace all of the test steps using the old activity.
3. Remove the old activity implementation.

Custom Java activities created in versions of OpenText Functional Testing prior to 12.00 will fail when you run your test.

Workaround:

1. Remove the ServiceTestCall.java interface from the project in which you created the custom Java activity..

2. Change the project package name to something other than hp.st.ext.java.

3. Add the ServiceTestCall.jar file to your classpath. This file is located in <Installdir>\Addins\ServiceTest\JavaCall\Java Interface\bin.

4. Recompile your Java project.