QTP/UFT 11.5 特性和安装的配置要求

This file provides the following information about UFT 11.51:

  • Getting Started
  • Minimum System Requirements and Supported Environments
  • What's New
  • Notes and Limitations
  • HP Support
  • Legal Notices

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.

Getting Started

Installing the UFT 11.51 Service Pack

  • The UFT 11.51 Service Pack can be installed only after you have installed UFT 11.50.
    • Important installation information and step-by-step installation instructions 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 DVD.
    • Alternatively, you can use the UFT 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.
  • The UFT 11.51 Service Pack does not update the Run Results Viewer. If you installed the Run Results Viewer with your UFT 11.50 installation, then you must also (separately) install the Run Results Viewer 11.51 Service Pack after installing UFT 11.51.

Installing and Using UFT on Windows 8 (Technology Preview)

Installation and use of UFT 11.51 on the Windows 8 operating system is not officially supported. It is provided at technology preview level only.

Before You Begin

Upgrading QuickTest or Service Test Assets

For QuickTest tests or components:

  • When trying to open a test or component saved in QuickTest 9.5, UFT will ask you if you want to upgrade the asset or open it in read-only mode.
  • If you try to open a test or component last saved in a version of QuickTest earlier than 9.5, an error message is displayed in the UFT Error Pane.
    • If the asset is saved in the file system, you must first open it in QuickTest 10.00 or 11.00 to upgrade it.
    • If the asset is saved in Quality Center or ALM, you must use the QuickTestAsset Upgrade Tool for HP ALM (available with the QuickTest Professional 10.00 or 11.00 DVD).
  • Assets last saved in QuickTest 10.00 or later can be opened in UFT.

For Service Test tests or components:

  • UFT 11.51 provides a Batch Upgrader command line tool, STBatchUpgrader.exe, located in the <UFT installation>/bin folder. This tool lets you run a batch file to upgrade tests last saved in Service Test, version 11.10 or 11.20, making them compatible for UFT 11.51.
  • If you do not upgrade your tests with the Batch Upgrader tool, when you open a test created in version 11.10 or 11.20, it prompts you to upgrade the test.

    For details, on the Batch Upgrader command line tool, see the UFT Help, available from the UFT Help menu.

  • For tests and components created in Service Test 11.00, you must first open and save them in Service Test 11.10, before you can upgrade them to UFT 11.51.
Useful Documents
  • After you install, you may want to refer to the following items, available from the UFT Help menu.
    • What's New. Provides details about new features and new environment support in UFT 11.50, compared to QuickTest 11.00 and Service Test 11.20. 
      (The What's New section of this Readme describes changes between UFT 11.50 and 11.51).
    • UFT Tutorials. If you are using UFT for the first time, use the UFT GUI Testing Tutorial and the UFT API Testing Tutorial to learn how to work with several of the most commonly used features.
    • UFT Help. A single-point of access for comprehensive product information, including installation guides, user guides, and language references in Help and/or PDF format. The Using this Help section describes how to navigate, use, and get updates for the Unified Functional Testing Help.

Hotfix and Patch Information

If you install a hotfix or patch over UFT 11.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 UFT Readme or any other UFT documentation, the information in the hotfix or patch readme takes precedence.

Documentation Updates

The top of this document contains the following identifying information:

  • Version number, which indicates the software version.
  • Publish date, which changes each time the document is updated.

To check for recent updates of this or any other UFT documentation, or to verify that you are using the most recent edition, visit the HP Software Product Manuals site and search under product name Functional Testing(requires an HP Passport).

Minimum System Requirements and Supported Environments

To successfully install and run UFT, your computer must meet the minimum system requirements shown below. However, performance may be improved by using systems with stronger/later setups than the minimum requirements.

For a complete list of all supported operating systems, browsers, and development environments, see the HP Unified Functional Testing Product Availability Matrix, available from the UFT Help Home page or the root folder of the Unified Functional Testing DVD, or get the latest version from the HP Software Product Manuals site (listed under product name Functional Testing). 

Computer Processor:
1.6 Ghz or higher
Operating System:
Windows XP Service Pack 3
Memory:
Minimum of 2 GB when no more than three add-ins are loaded simultaneously
Note:
  • An additional 512 MB of RAM are required when using a virtual machine.
  • Additional memory is required when loading more add-ins and when using the Save movie to results option to capture movies during run sessions.
Color Settings:
High Color (16 bit)
Graphics Card:
Graphics card with 64 MB 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).
Browser:
Microsoft Internet Explorer 7.0 or a later supported version


What's New

What's New in UFT 11.51 Service Pack

This section includes descriptions of new functionality and other changes in the UFT 11.51 Service Pack (compared to UFT 11.50). These changes apply to the following areas or features:

  • New Environment Support
  • Actions
  • Keyword View (Insert Report Step)
  • Run Session Stop Key
  • Errors Pane
  • Application Areas
  • Add-ins

For details about new functionality and environment support provided in UFT 11.50 and earlier, see the Unified Functional Testing What's New help, available from the UFT 11.50 Help menu.

New Environment Support

Support for the following environments was added in the UFT 11.51 Service Pack:

Environment
Newly Supported Version
Operating System
Windows 8 (Technology Preview level)
Web
Internet Explorer 10 (Technology Preview level)
 
Mozilla Firefox 16 and 17
PeopleSoft
PeopleSoft PeopleTools 8.52
SAP
SAP CRM 7
 
New SAP Web Dynpro ABAP 7.01 and 7.02 Controls.
For details, see the  SAP Add-in section of  What's New in UFT 11.51 below.
Siebel
Siebel 8.2.2
Terminal Emulators
Rocket BlueZone 6.x

For a complete list of all supported operating systems, browsers, and development environments, see the HP Unified Functional Testing Product Availability Matrix, available from the UFT Help or the root folder of the Unified Functional Testing DVD, or get the latest version from the HP Software Product Manuals site (listed under product name Functional Testing).

Actions
  • Action Templates. The Action Template feature supported in QuickTest 11.00 is supported in UFT 11.51. You may want to create an action template when you want to add the same element to each new action you create, such as the same comment, or the same ExecuteFile statement.
  • To create a new action template, create a text file containing all of the elements that you want to include in your template, and save it as ActionTemplate.mst, in the <UFT installation>\dat folder. TheActionTemplate.mst file must have the same structure and format as an action in the Editor.

  • External Action Properties. The External Action tab in the Action Properties dialog box, which was provided in QuickTest 11.00, is now also provided in UFT 11.51. This tab enables you to specify the data source for the selected action, and is available only when viewing properties for external actions.
  • The External Action tab provides the following options:

    • Use data stored with the original action (read-only). Uses the original action's data. If you select this option, the data is read-only when viewed from the calling test, and all changes to the original action's data sheet apply when the action runs in the calling test.
    • Use a local, editable copy. Uses an editable copy of the data in the test's data table. If you select this option, a copy of the called action's data sheet is added to the calling test's data table and is independent of the original action.
    • If the called action has parameterized steps that rely on new information in the original action's data sheet, enter the relevant column names and required data to the action sheet in the calling test manually.

Keyword View (Insert Report Step)

You can add report details to your test by If you right-clicking a step in the Keyword View and selecting Insert Step > Report.

In the dialog box, you can enter the following details:

  • Step status: PassedFailedDone, or Warning
  • The name of the report to include in the results
  • Details about the report
  • An image relevant to the report step
Run Session Stop Key

You can define a shortcut key or key combination that stops the current recording session (for GUI tests only) or run operation, even if UFT is not in focus or is in hidden mode.

In the Run Sessions pane in the Options dialog box (Tools > Options > General pane > Run Sessions node, click in the Stop command shortcut key field and then press the required key or key combination on the keyboard.

The default key combination is Ctrl+Alt+F5.

Note: It is important to define a shortcut that is not already defined for some other operation by the application being tested. If this is the case and:

  • you open the application manually before you click Record or Run, the shortcut defined in the application is applied for its original purpose.
  • you start a record or run session and UFT opens the application for you, the shortcut you define stops the session.
Errors Pane

When your test contains an unmapped repository parameter, the Errors pane displays the test name and path in the Item column.

Application Areas

You can associate function libraries and object repositories with an application area by right-clicking the <application area name> node in the Solution Explorer and selecting Associate Function Library or Associate Object Repository. The application area's function library or object repository is displayed in the document pane.

Add-ins

In addition to the information in this section, see also New Environment Support, above.

Web Add-in

  • Mozilla Firefox only: A new method, DialogExists, is available for Browser test objects. The DialogExists method checks whether a dialog box is currently open in the browser. This can be useful before using theBrowser.HandleDialog or Browser.GetDialogText methods.

Flex Add-in

  • UFT can recognize a Flex application that is opened by specifying the URL of the SWF file in an Internet Explorer address bar. There is no need to create a simple HTML wrapper file to test such a SWF file (as was required in UFT 11.50.
  • UFT can recognize Flex test objects in windowless Flex applications, when the root FlexWindow object is manually added to the object repository.
  • Note: The Navigate and Learn option is not supported for windowless Flex applications .

SAP Add-in

  • The Add-in for SAP Solutions now supports testing the following SAP Web Dynpro ABAP 7.01 and 7.02 Controls:
    • BreadCrumb (Link)
    • Button (SAPButton)
    • ButtonChoice (SAPButton)
    • ButtonRow (SAPButton)
    • CheckBox (SAPCheckBox)
    • CheckBoxGroup (SAPCheckBox)
    • DateNavigator (SAPCalendar)
    • DropDownByIndex (SAPList)
    • DropDownByKey (SAPList)
    • FileDownload (Link)
    • FileUpload (WebFile)
    • FormattedTextEdit (WebEdit and SAPButton)
    • InputField (SAPEdit)
    • LinkChoice (Link and SAPDropDownMenu)
    • LinkToAction (Link and SAPButton)
    • MessageArea (WebElement)
    • RadioButton (SAPRadioGroup)
    • RadioButtonGroupByIndex (SAPRadioGroup)
    • RadioButtonGroupByKey (SAPRadioGroup)
    • RoadMap (WebElement)
    • Table (SAPTable)
    • TabStrip (SAPTabStrip)
    • ToggleButton (SAPButton)
    • ToggleLink (Link)
    • ToolBarLinkChoice (Link and SAPDropDownMenu)
    • Tray (SAPiView)
    • Tree (SAPTreeView)
    • TriStateCheckBox (SAPCheckBox)
  • Performance has been improved for recording steps on SAP Web controls.
  • Errors related to failures in identifying certain SAP Web objects during a run session no longer occur, These errors caused steps on those objects to fail and UFT reported that the test object description was not unique or that the object was not found.

Notes and Limitations

This section includes the following:

  • Before You Install
  • Supplemental Information
  • Localization

Before You Install

This section includes information that is important for you to know before you install UFT.

  • You cannot install Microsoft Office 64-bit on a machine with UFT.
  • The Web Services Add-in that was provided with QuickTest is not included in UFT. Instead, use the UFT API testing features to test your Web Services.
  • If you need to work with your existing QuickTest Web Services Add-in assets in UFT, contact HP Software Support or your HP Software provider.

  • Before you can connect UFT to an ALM 11.50 server, your ALM administrator must install the ALM Integration Enablement Pack on the server. The enablement pack is available from HP Software Support.
  • Working with components and application areas stored in ALM 11.50 (with the ALM Integration Enablement Pack) as well as all functionality related to creating, editing or running business process tests inside UFT is provided only at a Technology Preview level.
  • UFT supports the Sentinel RMS License Manager version 8.4.0 as its concurrent license server. Earlier versions of the concurrent license server are not supported.
  • If you previously had QuickTest 11.00 installed on your computer and you installed one of the patches or hotfixes that added support for working with the Google Chrome browser (QPTWEB00088 or another Chrome-related patch or hotfix), you must delete your user profile in the Chrome browser before you can use UFT to test applications in Chrome.
  • To do this, open the Chrome Settings window in your Chrome browser. In the Users section, click the Delete this user button.

  • UFT does not support Windows user names with non-English letters. If you log in to Windows using a user name (with administrative privileges) that contains non-English characters and then install UFT, the installation may complete successfully, but you may not be able to open UFT or it may not behave correctly.
  • 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 UFT 11.51 while the QTPNET_00015 patch (a QuickTest 10.00 patch) is installed on your computer, UFT may behave unexpectedly.
  • Workaround:

    1. Open the Add/Remove Programs dialog box from the Control Panel.
    2. Display the installed patches by selecting the Show updates check box (or click the View Installed Updates button, depending on your operating system version.)
    3. Locate HP QuickTest in the list and check whether QTPNET_00015 for HP QuickTest Professional 10.00 QFE is listed as an installed update.
    4. If it is installed, click Remove to uninstall this patch before you install UFT 11.51.
64-bit Applications
  • If a user with administrator privileges installs the ALM Add-in for UFT or perform 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.
Documentation
  • The UFT Help Index tab contains only reference items, such as objects, methods, properties, and functions. It does not contain any entries from the user guides.
  • To search for information from all the documents in the UFT Help, use the Search tab.

  • On some operating systems or after installing certain Windows service packs or updates, you may not be able to view the content of some Help files.
  • Workaround:

    1. Right-click the CHM file in <UFT installation folder>\help, and click Properties.
    2. In the dialog box that opens, click Unblock.

      For details, see http://support.microsoft.com/kb/902225

Supplemental Information

Use the information in this section as a supplement to (or if relevant, an override of) the relevant information in the product documentation.

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 the following:

  • General
  • API Testing
  • GUI Testing: Web
  • GUI Testing: Silverlight
  • GUI Testing: Java
  • GUI Testing: Flex
  • GUI Testing: SAP GUI for Windows
  • GUI Testing: SAP Web
  • ALM and Business Process Testing
General
  • Text and text area checkpoints are not supported if the text in the selected area is in a non-English language.
  • UFT may stop responding during a debug run session in the following scenario: If there is a breakpoint at a function call from an associated function library, and you open the function library after the run stops at the breakpoint, and then you insert or remove a breakpoint on the first line of the called function.
  • On Windows Vista operating systems and higher, only the OCR text recognition mechanism is applied. This can affect text recognition features (such as text checkpoints and output values, GetVisibleText andGetTextLocation test object methods, and TextUtil.GetText and TextUtil.GetTextLocation reserved object methods).
  • If UFT closes unexpectedly while an asset is open from ALM, the asset may remained locked by ALM for more than fifteen minutes. In some cases, you may be able to reopen UFT and reopen the test, but when trying to save it, you will receive an error message indicating that the test entity is already locked by you.
  • Workaround: Wait fifteen minutes or more and try again.

API Testing
  • The Embed jar in Test option (of the Call Java Class activity) is not supported when creating tests on Windows XP.
  • To run the API sample flight application, you must have administrator privileges.
  • Changes you make in the user event code using the auto-completion drop down are not reflected in the canvas until you save the document.
  • UFT 11.50 does not support NTLM authentication.
  • The Batch Upgrader tool may not successfully upgrade tests stored in ALM 11.00 when working on Windows 2003.
  • When opening many tests in the same solution using one or more of the same Web services, UFT may develop a memory leak. 
    Workaround: Move the Web service to the file system or ALM repository. To do this, import a Web service and then, in the Toolbox pane, right-click the Web Service activity and and select Move to > File System Activities or ALM/QC Activities.
  • In Web service calls, if you add an element to an Any type array and rename it, the Link to Source button is not immediately available.
    Workaround: Reselect the step in the canvas and then access the Link to Source button.
  • In Data awareness, if you update an Excel data source and link properties to the new data source, the new values will not be reflected in ALM.
    Workaround: Open the Map Parameters dialog box in ALM's Test Plan module > Parameters tab, and remap the properties.
  • To enable test versioning in Quality Center version 10.00, create a file in the <QC installation folder>\repository\sa\DomsInfo\Metadata\TEST folder called ServiceTest.xml with the following content:
  • <?xml version="1.0" encoding="UTF-8" ?>

    <Test Type="SERVICE-TEST">

    <Repository>

    <Folders ID="1" Filter="." BlindCopy="true" />

    </Repository>

    <Versioning Enabled="true" />

    <Baselining Enabled="false" />

    </Test>

  • The Run Step command, for steps whose properties are assigned an XML data source, does not retrieve the latest data shown in the user interface.
    Workaround: Save the test before activating the Run Step command.
GUI Testing: Web
  • Any limitations described in the UFT product documentation for Google Chrome are also relevant for Google Chrome Frame. Additionally, in Google Chrome Frame:
    • You cannot delete browser cookies.
    • If your script navigates from one page to another in Google Chrome Frame, the next line in the script may take some time to execute.
  • Web Add-in support on Chrome versions 23 and higher is disabled for some web sites. In such cases, Chrome prompts you to manually approve the QTP Agent. To continue testing, do one of the following:
    • In the prompt, click Always on this site to approve the QTP Agent Chrome plug-in for the Web site you are working with.
    • Approve the plug-in on all Web sites by modifying the chrome settings to always allow the QTP Agent.
    • Close Chrome and then relaunch it using the following script:
      SystemUtil.Run "Chrome.exe","--always-authorize-plugins http://Url/To/Your/Site
  • UFT does not support accessing browser dialog boxes (such as alert, confirmation, or prompt) directly in Mozilla Firefox.
  • Workarounds:

    • Use the HandleDialog or GetDialogText methods described in the Web section of the HP Unified Functional Testing Object Model Reference.
    • If the Browser("xxx").Page("xxx").Dialog("xxx") object is recognized, either use a recovery scenario with the HandleDialog method, or a Browser("xxx").Page("xxx").Dialog("xxx").Type step to handle the pop-up dialog box. For example, use an Enter key to click the default button and close the dialog box.
  • To test your Web application in Mozilla Firefox, you must enable the Unified Functional Testing Extension in one of the following ways:
    • If the Select Your Add-ons screen is displayed when you open Firefox, select to keep the Unified Functional Testing Extension 11.50.
    • If the Install Add-on tab opens and displays Unified Functional Testing Extension 11.50 when opening Firefox, select the Allow this installation check box and click Continue.
    • Otherwise:
    • 1. In Firefox, select Tools > Add-ons.

      2. In the General tab, click Manage Add-ons.

      3. In the Add-ons Manager tab, select the Extensions node.

      4. In the Unified Functional Testing Extension 11.50 row, click the Enable button.

  • If you try to use a Text Area Checkpoint or Text Area Output Value step on a Web application, the text recognition functionality may not always be reliable.
  • For details, see the following section of the UFT User Guide, which is also relevant for Web-based applications:

    HP Unified Functional Testing User Guide > GUI Testing: Checkpoints and Output Values > Text Recognition for Windows-Based Objects > Guidelines for Text Recognition

    Workaround: Use the Text Checkpoint or Text Output Value option for Web-based applications, instead of Text Area Checkpoint/Output Value.

GUI Testing: Silverlight
  • Silverlight out-of-browser applications are supported only in supported Windows operating systems that are earlier than Windows 7 or Windows Server 2008 R2.
  • Low-level recording is not supported for Silverlight objects created in version 5 when opened in Firefox browsers versions 3.6.4 or later.
GUI Testing: Java
  • The Java Add-in JRE Support Tool is supported only when working with the Oracle Java JRE version 5 or 6.
GUI Testing: Flex
  • When recording, if you select an item from a FlexMenu object that has the same name as another item in the object, the step is recorded using the item name instead of the item index.
  • Workaround: In the editor, change the item name recorded in the step to the item index.

GUI Testing: SAP GUI for Windows
  • The SAP Gantt chart (SAP Bar Chart) and Image/Picture controls are supported by the SAP GUI for Windows alternative recording mechanism. However, the current support for these controls is limited. You can override the default recording behavior for SAP Windows test objects, or add limited recording support for other SAP GUI for Windows objects.
GUI Testing: SAP Web
  • While recording some SAPEdit objects, if you enter a value and immediately press the Enter key, a Set step is added to the test without the required Submit step. This may cause the test run to fail.
  • Workarounds:

    • While recording, wait a few seconds after entering a value and before pressing the Enter key.
    • While recording, click anywhere on the screen between entering the value and pressing the Enter key.
    • Manually add the required Submit step to your test.
  • When performing an SAPCalendar.SetDate step on a bi-monthly display calendar control, the date must be visible in the application.
  • During a run session, the SAP platform response time may be slower than the time it takes for UFT to run the corresponding step.
  • Workaround: Add a Wait statement prior to the relevant step.

  • When recording and running steps on a table control, only the table content that is visible on the client is actually available.
ALM and Business Process Testing
  • The following characters are not supported for folder names and files in ALM: \ / : * ? " < > | % ' ;
  • If you have existing folders in ALM that contain UFT entities and have one or more of these characters in the folder name, rename the ALM folder or move the entities to another folder before working with those entities in UFT. Otherwise, your run session may fail or other unexpected behavior may occur.l

  • If you run a business process test in Debug mode and the components in the test contain breakpoints, and then you later run the same business process test in Normal mode, the test will continue to stop at the breakpoints
  • Workaround: Before running the test in Normal mode, manually remove all breakpoints from the individual business components.

  • When working with ALM Data Awareness, if you update an Excel data source and then link properties to the new data source, the new values will not be reflected in ALM.
    Workaround: Open the Map Parameters dialog box in ALM's Test Plan module > Parameters tab, and remap the properties.
  • If you use the Launch button in ALM to open an application area in UFT, you cannot add function libraries to the application area.
  • Workaround: Open UFT manually and then open the application area and add the function library.

  • Before running an API test that calls a GUI tests from ALM, you must either ensure that UFT is open with a solution open, or you must close UFT. The test will not run if UFT is open with no open solution.

Localization

  • Some user interface items are not localized, for example:
    • Tooltips in the Properties Pane
    • Tooltips and context menu in the editor of the File Content Checkpoint dialog box
    • Context menu for the search box in the toolbar of the File Content Checkpoint Properties dialog box
    • Compilation information in the Output pane for an API Test
    • Error messages when importing a WSDL Web service
    • The default value string for a Date parameter in the Add Input Parameter dialog box for an API test
    • Warning or error messages in the Test Batch Runner, for example, when saving files using the Save As command
    • Strings displayed when adding a date-type input parameter in the Properties pane of an API test
    • Some of the UFT user interface related to XML operations
    • XML Validation results in the Run Results Viewer

Workaround: Install the relevant user interface language .NET Framework Language Pack. You can download it from the Microsoft download center: http://www.microsoft.com/en-us/download/default.aspx

  • The image displayed when selecting View Sample Snapshot in the Asset Comparison tool is not localized

你可能感兴趣的:(测试,惠普,qtp)