HP Unified Functional Testing Readme
Software Version: 12.51
Document Release Date: September 2015
Software Release Date: September 2015
The most updated version of this Readme is located here (requires an HP Passport).
To check for recent updates of any other UFT documentation, or to verify that you are using the most recent edition, visit the HP Software Product Manuals site (requires an HP Passport).
This file provides the following information about UFT 12.51:
Minimum and Recommended System Requirements and Supported Environments
Note: If the information in this Readme conflicts with information in any other UFT documentation released at the same time, the information in this Readme takes precedence.
UFT 12.51 expands its integration with other HP's testing solutions with new features and enhancements for greater usability, productivity, and technology support, including:
Support for Mobile hybrid applications: UFT can now create Web test objects for the Web objects in your hybrid apps and in the HP Mobile Web app.
Expanded LeanFT capabilities: LeanFT further extends its abilities to help you create tests, including:.
Connect LeanFT to HP Mobile Center to test your mobile applications
Run your LeanFT tests from ALM
Test Java and SAP GUI for Windows objects in your AUTs
HTML Report enhancements
New supported environments: Visual Studio 2015, Windows 10, Eclipse Mars (4.5), Firefox 25-26
For details on these new features, see http://leanft-help.saas.hp.com/en/12.51/HelpCenter/Content/HelpCenterRoot/WhatsNew.htm in the LeanFT Help Center.
Atlassian Bamboo support: UFT expands its coverage of continuous integrations by enabling you to run UFT tests on an Atlassian Bamboo server.
Greater BPT testing capabilities: BPT in UFT is now more comprehensive and easier to use. You can do the following:
Product enhancements, including:
New Technology Support: UFT now supports the following technologies and platforms:
Windows 10
QT 4.8 applications built with Visual Studio 2008 or mingw gcc 4.8.2
TE Attachment Reflection for UNIX open VMS 14.1
TE Attachmate Extra! X-treme 9.3
Flex 4.14
SiebelOpenUI 8.1.1.14 SIA
You can upgrade directly to UFT 12.51 from any previous version of UFT or from Service Test 11.50.
If you are upgrading from any version of QuickTest or from Service Test version 11.20 or earlier, you must manually uninstall this version and install UFT 12.51.
After upgrading to UFT 12.51 from a version of UFT, QuickTest, or Service Test earlier than 12.50, you must retrieve a new license key and install it . You can upgrade your license at:
For existing customers | www.hp.com/software/updates (you need to enter your SAID number) |
For new customers | http://h30580.www3.hp.com |
Full license installation instructions can be found in the HP Unified Functional Testing Installation Guide. For additional details, you can also view a presentation at https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01778685 .
The path in which installation files for UFT are located, and the path in which UFT is installed, can contain only English characters.
If you install UFT12.51 while the QTPNET_00015 patch (a QuickTest 10.00 patch) is installed on your computer, UFT may behave unexpectedly.
To remove the patch:
Important installation information and step-by-step installation instructions for UFT can be found in the HP Unified Functional Testing Installation Guide. The Installation Guide is available in PDF format in the root folder of the Unified Functional Testing installation pacakage.
Alternatively, you can use the HP Unified Functional Testing Installation QuickStart Sheet, which provides the details you need to know for a standard UFT installation in a single, two-sided sheet.
You can also open these documents from the Unified Functional Testing Help after you install UFT.
By default, the silent UFT installation does not configure the DCOM settings that are required for remotely controlling UFT using automation scripts.
To instruct the installation to configure the DCOM settings for automation scripts, add ALLOW_RUN_FROM_ALM=1
and ALLOW_RUN_FROM_SCRIPTS=1
to your silent installation command. For more detail, see the HP Unified Functional Testing Installation Guide.
Caution: Configuring these DCOM settings may expose the UFT computer to security risks.
If the HP UFT Files in Use dialog box is displayed during the installation process:
Select the Close the application and attempt to restart them option.UFT automatically closes the needed applications and continues the installation.
If you are upgrading from an earlier version of UFT, restart the computer before upgrading.
If after restarting, the HP UFT Files in Use dialog box lists Explorer as the open application, you can do one of the following:
If you upgrade to UFT 12.51 from an version of UFT earlier than 12.50 shortly after using UFT to run GUI tests from ALM, make sure to stop the Remote Agent (if running) before running tests from ALM again. To stop the previous Remote Agent process, in the Windows system tray, right-click the Remote Agent icon and select Exit.
If you are using the UFT Add-in for ALM and plan to work with ALM version 11.52, you must ensure that the Microsoft Visual C++ 2005 SP1 Redistributable Package is installed on your computer. You can download this package file from http://www.microsoft.com/en-us/download/details.aspx?id=5638.
Connecting to ALM via UFT on Windows 10 without administrative privileges is not supported.
Workaround: Connect to ALM with Administrator permissions immediately after performing your UFT installation.
If you used UFT 12.00 to test Web applications on Safari, then after you upgrade UFT you must reinstall the UFT Connection Agent on the Mac from the current UFT version.
The UFT Connection Agent preferences and the Unified Functional Testing Agent Safari extension preferences are reset to their defaults.
If you want to use non-default preferences, for example, if you configured UFT to use a port other than the default 8822 for remote connections, then you must reconfigure these preferences on the Mac computer.
This is required because of significant changes in the UFT Connection Agent's preferences, due to security enhancements in UFT 12.01. For example, the UFT Connection Agent now uses different ports to communicate with UFT and the Safari extension.
For more details on what you can configure for the UFT Connection Agent, see the section on the UFT Connection Agent in the Web section of the HP Unified Functional Testing Add-ins Guide.
If you plan to run tests of a Web Service using security created using Service Test or UFT 11.53 or earlier, you must have the .NET Framework 3.5, WSE 2.0sp3 package, and WSE 3.0 package installed on your computer.
These prerequisites are not provided with the UFT installation. If they are not installed on your computer, you can install them from the following locations on the DVD:
NET 3.5 Framework:DVD/prerequisites/dotnet35_sp1/donetfx35_sp1.exe
WSE 2.0 sp3: DVD/prerequisites/wse20sp3/MicrosoftWSE2.0SP3Runtime.msi
WSE 3.0: DVD/prerequisites/wse30/MicrosoftWSE3.0Runtime.msi
For QuickTest tests or components: |
|
For Service Test tests or components: |
|
If you install a hotfix or patch over UFT 12.51, information about that patch is described in the corresponding hotfix or patch readme.
If the information in a hotfix or patch readme conflicts with information in the HP Unified Functional Testing Readme or any other UFT documentation, the information in the hotfix or patch readme takes precedence.
This section includes:
The information in this section is up-to-date at the time of this release. Refer to https://hpln.hp.com/page/uft-system-requirements for the most updated system requirements list.
For a complete list of all supported operating systems, browsers, and development environments, see the HP Unified Functional Testing Product Availability Matrix. Download the latest version from the HP Software Support site or via the HP Support Matrix page site.
Note: You must have an HP Passport to access the HP Unified Functional Testing Product Availability Matrix.
Minimum | Recommended | |
Computer Processor: | 1.6 Ghz or higher | 3 Ghz or higher |
Operating System: | Windows 7 Service Pack 1 (32-bit or 64-bit) | Windows 7 Service Pack 1 (32-bit or 64-bit) |
Memory: |
Minimum of 2 GB when no more than three add-ins are loaded simultaneously Note:
|
4 GB or more of RAM |
Hard Disk Drive: | 5400 RPM | 7200 RPM or faster |
Color Settings: | High Color (16 bit) | High Color (32 bit) |
Graphics Card: | Graphics card with 64 MB video memory | Graphics card with 64 MB or more video memory |
Free Hard Disk Space: |
2 GB of free disk space for application files and folders You must also have an additional 1 GB of free disk space on the system disk (the disk on which the operating system is installed). |
20 GB of free disk space for application files and folders You must also have an additional 1 GB of free disk space on the system disk (the disk on which the operating system is installed). |
Browser: | Microsoft Internet Explorer 8.0 | Microsoft Internet Explorer 9.0 |
Prerequisite Software Requirements |
If you do not have these programs installed, UFT prompts you at the beginning of the installation to install them. |
Note: Additional troubleshooting information, guidelines, and feature-specific limitations are described in the relevant locations of the installation and product documentation. Make sure you are aware of those issues when working with the relevant features.
This section includes important notes and known limitations and workarounds:
You cannot install Microsoft Office 64-bit on a machine with UFT.
Workaround:
Re-install the Microsoft Office Access database engine from the prerequisites\msade2010 folder of the UFT12.51 setup directory, using the following command:
<UFT root directory>\prerequisites\msade2010\AccessDatabaseEngine.exe /passive
The version of the pdm.dll file installed with the Microsoft Script Debugger (which is part of UFT’s Additional Installation Requirements) is obsolete and can cause problems when you try to debug GUI tests. If you want to debug GUI tests in UFT, make sure that you have a newer version of this file installed and registered.
The pdm.dll file is installed and registered with Microsoft Visual Studio and Microsoft Office. It is also installed, but not registered, with Microsoft Internet Explorer (version 8 and above).
If the currently registered version of the pdm.dll file is lower than 9, then uninstall the Microsoft Script Debugger (if installed) and repair the installation of the last of these products to be installed. (Check registry for pdm.dll version: HKEY_CLASSES_ROOT\CLSID\{78A51822-51F4-11D0-8F20-00805F2CD064}\InprocServer32
)
If you need to use the pdm.dll file installed with Microsoft Internet Explorer, make sure you have administrator privileges and do the following:
Locate the pdm.dll file.
This file is usually located in c:\program files(x86)\internet explorer\ or c:\program files\internet explorer.
Move the pdm.dll file and the msdbg2.dll file from the same folder to a different location (registering them from the original location behaves differently).
Run the following commands:
regsvr32 <full path to pdm.dll>\pdm.dll
regsvr32 <full path to pdm.dll>\msdbg2.dll
Sprinter: If you are using both UFT and Sprinter on the same computer, and you uninstall either UFT or Sprinter, you must run a Repair for the installation of the remaining product.
In the Custom Setup screen, it is possible to select the LeanFT Visual Studio or Eclipse plugins even if you do not have the relevant IDE installed at the time of the installation. If you install the IDE later, you will not have the LeanFT plugin available.
Workaround: After installing the required IDE, run a Repair for the installation.
When using UFT on Windows 8.X or higher or Windows Server 2012 R2, if you want to use API tests and components, make sure that you have MSU (Microsoft Update) KB2887595 installed.
If you are testing applications in Google Chrome version 31 or later, Chrome automatically downloads and installs the HP Functional Testing Agent for Google Chrome the first time you open Chrome after UFT is installed.
Note: If you are using a version of the Functional Testing Agent for Google Chrome from UFT version 12.00 or earlier, you must enable the downloaded extension and remove the previous version of the Functional Testing Agent extension.
In the following cases, you must manually enable the Functional Testing Agent for Google Chrome extension:
You have no internet connection.
You have not enabled the automatic updates for Google Chrome.
You are using Google Chrome version 30 or earlier.
For details on manually enabling the extension, see the task on How to Enable the Functional Testing Agent for Google Chrome Extension in the Web section of the HP Unified Functional Testing Add-ins Guide.
If you are testing applications in Firefox version 33 or later, accept the prompt for install HP Functional Testing Agent for Firefox the first time you open Firefox after UFT is installed.
If you testing applications in Firefox version 32 and earlier, do the following:
If you previously used the Frame.RunScript, Frame.RunScriptFromFile, Page.RunScript, or Page.RunScriptFromFile methods in your tests of a Web site or Web application, you should update the RunScript argument to use either an eval function or an anonymous function.
For example, if you used this syntax previously:
Browser("MySearchEngine").Page("MySearchEngine").Frame("Web Search").RunScript "var remove = document.getElementById('logo'); remove.parentNode.removeChild(remove)"
you should update this to:
Browser("MySearchEngine").Page("MySearchEngine").Frame("Web Search").RunScript "eval(var remove = document.getElementById('logo'); remove.parentNode.removeChild(remove););"
OR
Browser("MySearchEngine").Page("MySearchEngine").Frame("Web Search").RunScript "(function(){var remove = document.getElementById('logo'); remove.parentNode.removeChild(remove);})();"
This section is relevant if you install LeanFT from the UFT installation.
Changes may be required to tests created in LeanFT 12.50:
WPF. The WPF Slider.Value (C#) and Slider.getValue (Java) statements from LeanFT 12.50 are obsolete. They have been replaced with: WPFSlider.Position (C#) and WPFSlider.getPosition (Java).
If you have tests that used this obsolete property or method, you must modify those tests to use the new name.
SAP UI5.
The names of the following SAPUI5 test objects were changed as follows:
IToolbar (C#) and Toolbar (Java) were renamed to IToolBar (C#) and ToolBar (Java)
ITextEdit (C#) and TextEdit (Java) were renamed to IEditField (C#) and EditField (Java)
ITree (C#) and Tree (Java) were renamed to ITreeView (C#) and TreeView (Java)
In the SAPUI5 Calendar and TextEdit (now renamed to EditField) objects, the Name property (C#) and getName method (Java) were renamed to Title property (C#) and getTitle method (Java).
If you have tests that used these obsolete test objects, properties, or methods, you must modify those tests to use the new names.
Additionally, if you have SAPUI5 test objects in your existing application models that use the obsolete type names, you must update those application models to use the new names.
Additional LeanFT 12.51 notes and limitations are available at: http://leanft-help.saas.hp.com/en/12.51/HelpCenter/Content/HelpCenterRoot/ReleaseNotes.htm.
If a user with administrator privileges installs the Unified Functional Testing Add-in for ALM or performs a Repair operation on the Run Results Viewer, and then you or another user runs UFT on that computer as a user without administrator privileges (without write permissions to the HKCR hive in the registry), UFT will lose its support for 64-bit applications.
Workaround: Log in as an administrator and do one of the following:
Repair UFT
Double-click <UFT installation>\bin64\Mediator64.exe
If your computer has two versions of an application, where one is 32-bit and the other is 64-bit (for example, calc.exe), then UFT always opens the 32-bit version when it performs a step to open that application. This occurs when the operating system performs a redirect from the Program Files folder to the Program Files (x86) folder, and from the System32 folder to the SysWow64 folder.
Workaround: To specify a 64-bit version, make sure that the step explicitly states the path to the 64-bit application. For example, you can copy the 64-bit application to any folder (other than the Program Files folder that is redirected to Program Files (x86)) and specify that path instead.
When working with .NET or WPF Add-in extensibility for a 64-bit Windows Forms process, the custom server DLLs must be built using the Any CPU option.
On some operating systems or after installing certain Windows service packs or updates, you may not be able to view the content of the CHM-based Advanced References Help files.
Workaround:
You can visit the HP Software Support web site at: https://softwaresupport.hp.com
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can: search for knowledge documents of interest, submit and track progress on support cases, submit enhancement requests online, download software patches, and more.
To access the self-solve knowledge base or to search for the latest versions of HP Software manuals, visit the Knowledge and Manuals Library.
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: https://softwaresupport.hp.com and click Register.
To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 1992-2015 Hewlett-Packard Development Company, L.P.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Google™ and Google Maps™ are trademarks of Google Inc
Intel® and Pentium® are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®, Windows® XP, and Windows Vista ® are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Send documentation feedback to HP