<configuration> <startup> <supportedRuntime version="v1.1.4322"/> </startup> </configuration>
We’ve provided you with a list of answers to frequently asked questions about the Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software product, and how it works with the Ultimate UI for Windows Forms product:
Currently, each volume release of Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software maps directly to the corresponding release of Ultimate UI for Windows Forms. Therefore, Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 21.1 is supported to work only with Ultimate UI for Windows Forms 21.1.
Test Automation for Micro Focus Win-Forms (Unified Functional Testing) 21.1 supports the following versions of QuickTest Professional: 9.0, 9.1, 9.2, 9.5, 10 and 11. It also supports QuickTest Professional .NET Add-in 9.2, 9.5, 10 and 11.
No, Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software will work regardless of the Hot Fixes applied. However, if you upgrade an Ultimate UI for Windows Forms volume release, you must upgrade Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software to the corresponding volume release.
Yes, each version of Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software will be backward-compatible. If there is a need to break backward compatibility in order to support additional functionality, the changes will be documented and made available to you.
The Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software Version Utility was added in the 2005 Volume 2 release to resolve this problem of running multiple versions of the product. The utility is compatible with Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 2004 Volume 3 and later.
While only Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 2006 Volume 1 and later are fully integrated into the additional functionality introduced in QuickTest Professional 9.0, Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 2005 Volume 3 release and earlier will function with all supported QuickTest Professional versions.
New scripts can be recorded using QuickTest Professional 9.0. However, the new enhanced Keyword View functionality introduced in QuickTest Professional 9.0 will not be available for these Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software versions. This new feature is available only with Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 2006 Volume 1 and later.
QuickTest Professional does not support multi-monitor record and replay. Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software inherits this limitation from QuickTest Professional.
This happens because there is a lock on the SwfConfig.xml file that does not allow the file to be modified. To resolve this:
Follow the steps to manually set up Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software, as explained in Manually Setting Up Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software .
Delete the temp file ~GLBS383.TMP, if it exists in:
QuickTest Professional 9.2 and earlier:
C:\Program Files\Mercury Interactive\QuickTest Professional\dat\
QuickTest Professional 9.5 and later:
C:\Program Files\HP\QuickTest Professional\dat\
There is a problem with the Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software installation. This usually means that the SwfConfig.xml file was not properly updated during the install. Follow the steps to manually set up Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software, as explained in Manually Setting Up Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software .
There is a problem with the Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software installation. The SwfConfig.xml was probably updated. However, either the Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software assemblies cannot be located, or the test application was compiled with the wrong version of Ultimate UI for Windows Forms.
You may be running a trial version of Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software, and the license has expired. You need to uninstall Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software, or purchase a license.
Note: Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software licensing is similar to Ultimate UI for Windows Forms licensing.
Yes, Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software will record and replay actions on sub-classed Ultimate UI for Windows Forms controls. It will record all the actions inherited from the Ultimate UI for Windows Forms control. However, it will not record any new events/actions that were added by the customization of the Ultimate UI for Windows Forms (even though the user can add some script to force new events to get fired).
When the Microsoft .NET Framework 2.0 is installed on the test machine, QuickTest Professional 8.2 uses the .NET Framework 2.0 by default. There is a known limitation when using this version of the framework where .NET classes cannot be exported to COM unless all inherited interfaces can be viewed by COM. This means if one of the inherited interfaces has the following attribute: [ComVisible(false)] the Object cannot be passed to VBScript.
Note: This issue has been resolved for Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software 2005 Volume 3 (CLR 2.0) versions and later.
To solve this issue for versions prior to 2005 Volume 3 (CLR 2.0), QuickTest Professional needs to be forced to use .NET Framework 1.x. This is done by creating a config file named "QTPro.exe.config" and placing it in the Bin folder of the QuickTest Professional install directory. This config file should include the following configuration information (with the appropriate build number of the .NET Framework that is installed on the test machine):
<configuration> <startup> <supportedRuntime version="v1.1.4322"/> </startup> </configuration>
You can switch between CLR 1.x and CLR 2.0 versions of Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software using the Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software' Version Utility.
You will also need to configure QuickTest Professional to run under the same framework as your Application Under Test. You can do this by updating the version attribute of “supportedRuntime” node in "QTPro.exe.config" file. This file will be found in the Bin folder of QuickTest Professional install directory.
Note: The "QTPro.exe.config" file does not exist by default for QuickTest Professional 8.2. To create it, see the previous Frequently Asked Question.
You can uninstall Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software by using the Add/Remove programs Control Panel menu item.
Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software does not need additional requirements over that of Micro Focus UFT, except for the free disk space required. A full install of Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software is under 30MB.
There are two scenarios that may occur when you are upgrading your version of QuickTest Professional.
It may clear the swfconfig.xml located in the QuickTest Professional dat directory.
It may clear the registry entries pertaining to the TypeInformation files.
The reason these instances may occur is because these are files and registry entries that we add to QuickTest Professional. These files and registry entries may get cleared depending on the upgrade types.
We recommend that you run the Version Utility after you upgrade from one version of QuickTest Professional to another. This will correct any problems with the swfconfig.xml file.
You can recognize if your TypeInformation files registry entries are missing if the intellisense for Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software specific methods are missing. If they are missing, follow step 4 in Manually Setting Up Test Automation for Micro Focus Win-Forms (Unified Functional Testing) software.