Troubleshooting and Limitations - Running the Support You Designed

This section describes troubleshooting and limitations for developing your support set.

During a recording session, the custom server mapped to your custom control is only created after some operation takes place on the custom control itself.

If you design the GetWndMessageFilter method to specify that your custom server will handle messages that occur on other controls, such messages can only be handled after the custom server is created.

Therefore, for example, you may have to click on the custom control before the custom server can receive and process messages on other controls in the application.

Depending on how you implement support for recording on your custom control, you might want to provide instructions regarding this issue to the UFT One users who use your support set.

When using the .NET Add-in Extensibility API with Microsoft .NET Framework 1.1, a General Run Error may occur while running your test. This is caused by an Execution Engine Exception error in the application under test (AUT).

Workaround: Install Service Pack 1 (or later) for Microsoft .NET Framework 1.1.

When using an XML-based Custom Server, if you have more than one version of Microsoft .NET Framework installed, a run-time error might occur during the run session. The error message in the log file indicates that the configuration file contains a compilation error. This is because assemblies compiled with Microsoft .NET Framework version 2.0 and later are not recognized by earlier versions of Microsoft .NET Framework.

Workaround: Perform one of the following:

  • Solution 1: In the Registry, in the following key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFrameworkadd the following DWORD Value "OnlyUseLatestCLR"=dword:00000001

  • Solution 2: If the .NET application you are testing has a configuration file, add the following information to the file:

    <configuration>
      <startup>
            <supportedRuntime version="v2.0.50727"/>
      </startup>
</configuration>

    • The configuration file must be named <executable_name>.exe.Config and be located in the same folder as the executable of the .NET application you are testing.