hp qtp 10.00 readme

HP QuickTest Professional 10.00 Readme

Software version: 10.00

DocuPublish date: January 2009

This file provides the following information about the QuickTest Professional 10.00 version:

Documentation Updates on page 1

Whats New in QuickTest Professional 10.00 on page 4

System Requirements on page 9

Supported Environments and Programs on page 11

HP Unified Functional Testing on page 15

Useful Information on page 16

Notes and Limitations on page 31

Multilingual Support on page 98

Third-Party License Agreements on page 102

HP Support on page 103

Legal Notices on page 104

mentation Updates

The first page of this readme document contains the following identifying information:

Version number, which indicates the software version.

Publish date, which changes each time the document is updated.


2

To check for recent updates or to verify that you are using the most recent edition, visit the following URL:

http://h20230.www2.hp.com/selfsolve/manuals

This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html

Or click the New users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

Note: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL: www.adobe.com.

QuickTest Professional Documentation

Important installation information and step-by-step installation instructions can be found in the HP QuickTest Professional Installation Guide. The HP QuickTest Professional Installation Guide is available in PDF format in the root folder of your DVD. You can also find it in the folder after you install QuickTest.

If you are using QuickTest Professional for the first time, use the QuickTest Professional Tutorial (Help > QuickTest Professional Tutorial) to learn how to work with the most commonly used features.

The Whats New Help (Help > Whats New) provides information about new features and supported environments in this version of QuickTest Professional.


Comprehensive information about QuickTest Professional can be found in the QuickTest Professional Help (Help > QuickTest Professional Help). This global Help window includes the HP QuickTest Professional User Guide, the HP QuickTest Professional for Business Process Testing User Guide, the HP QuickTest Professional Add-ins Guide, the HP QuickTest Professional Object Model Reference, the QuickTest Professional Advanced References section, which includes a number of automation and schema references, and the Microsoft 3

VBScript Reference. Several of these guides are also available in PDF format (accessible from the Help > Printer-Friendly Documentation page).

Hotfix and Patch InformationIf you install a hotfix or patch over QuickTest Professional 10.00, information about that patch is described in the corresponding hotfix or patch readme.

To view the QuickTest Professional hotfix and patches installed on your computer, open QuickTest, select Help > About QuickTest Professional and click the Product Information button. Installed hotfixes and patches are listed at the bottom of the Product Information page. Click the link to open the readme file for the hotfix or patch. You can also view readme files for all installed hotfix and patches in the \HotfixReadmes folder.

If the information in a hotfix or patch readme conflicts with information in the QuickTest Professional Readme or any other QuickTest Professional documentation, the information in the hotfix or patch readme takes precedence.

Note: If you do not have a working Windows Installer 3.1 on your computer, you will not be able to install QuickTest Professional hotfixes and patches. For information and download, see http://www.microsoft.com/downloads/details.aspx?FamilyID=889482FC-5F56-4A38-B838-DE776FD4138C&displaylang=en.


4

Whats New in QuickTest Professional 10.00

QuickTest Professional 10.00 brings you an exciting array of new features, supported environments, and other enhancements. The following provide a short summary of these. See the What's New Help to learn more. (In QuickTest, select Help > Whats New.)This section includes:

New Features on page 4

New Supported Environments on page 7

Enhancements on page 8

New FeaturesQuickTest Professional 10.00 now offers the following new features.

Centrally Manage and Share Testing Assets, Dependencies, and Versions in Quality Center 10.00

QuickTest Professional 10.00 has a powerful set of new Quality Center 10.00 integration capabilities for QuickTest assets.*

These integration capabilities include:

New resources and dependencies model for storing and managing shared assets

Support for asset versioning and baselines

Asset Comparison Tool for comparing versions of individual QuickTest assets and Asset Viewer for viewing an earlier version of a QuickTest asset

A special tool for Quality Center administrators that upgrades all QuickTest assets to use these new features.

* QuickTest assets include tests, components, application areas, and the resources associated with them, such as shared object repositories, function libraries, recovery scenarios, and external data tables.


Perform Single-User Local System Monitoring While Running Your Tests

The new local system monitoring feature (File > Settings > Local System Monitor) enables you to monitor the local (client-side) computer resources used by the application instance you are testing during a run session.

You can monitor a number of different system counters to view the effects 5

your application has on the system. You can also define upper limits for the counters. If any of the specified counters exceed these limits, the test run will fail.

Additionally, you can export the data from the System Monitor tab to a variety of file types.

Improve Portability by Saving Copies of Tests Together with Their Resource Files

If you need to open or run a test when you do not have access to the network drive or Quality Center, you can use the File > Save Test with Resources command. This saves a standalone, local copy of your test, all associated resource files, and any called actions.

Call Actions Dynamically During the Test Run

You can use the new LoadAndRunAction statement to load an action only when the step runs, and then immediately run that action. This is useful, for example, if you use many conditional statements that call external actions, and you do not want to load all of these actions each time you open the test, since these actions may not be necessary during the run session.


6

Develop Your Own Bitmap Checkpoint Comparison Algorithm

You (or a third party) can now develop custom comparers for bitmap checkpoints. A custom comparer is a COM object that performs the bitmap comparison for the checkpoint according to your testing requirements. When QuickTest performs a bitmap checkpoint that uses a custom comparer, it supplies the expected and actual bitmaps to the custom

comparer object. QuickTest then receives and reports the results that the custom comparer returns.

For information on how to create custom comparers, see the Bitmap Checkpoint Customization appendix of the HP QuickTest Professional User Guide in the QuickTest 10.00 Help.

Centrally Manage Your Work Items and ToDo Tasks in the To Do Pane

The new To Do pane enables you to create and manage self-defined tasks, and to view a compiled set of the TODO comments from your tests, components, and associated function libraries.

Improve Test Results Analysis with New Reporting Functionality

When you want to know more about a particular node in the Test Results window, right-click it and select Jump to Step in QuickTest to display that step within the QuickTest testing document.

You can export your QuickTest run results to Microsoft Word or PDF formats.

When you use the Reporter.ReportEvent method to add information to the run results, you can specify an image file as the fourth argument.

In addition to the expected and actual bitmaps of bitmap checkpoint results, you can also select to view an image showing only the differences between the two.

When you select the Detailed option for printing or exporting run results, the document now includes all images.

The run results for tests and components that are run as part of a Quality Center test set now include the Quality Center server and project name.


Test Standard and Custom Delphi Objects

The new Delphi Add-in enables you to test Win32 VCL Delphi controls

Delphi Add-in Extensibility enables you to develop support for applications that use third-party and custom Delphi controls.7

New Supported EnvironmentsIn addition to environments supported in earlier versions, QuickTest now supports the following operating systems, browsers, and development environments:

Microsoft Windows 2008 Server 32-bit Edition

Microsoft Windows 2008 Server 64-bit Edition

Microsoft Windows Vista, Service Pack 1, 32-bit Edition

Microsoft Windows Vista, Service Pack 1, 64-bit Edition

Microsoft Windows XP Professional 32-bit EditionService Pack 3

Citrix Presentation Server 4.5

Microsoft Internet Explorer 8.0 Beta 2

Mozilla Firefox 3.0.x

Delphi: IDE, versions 6, 7, and 2007 (for controls based on the Win32 VCL library)

SAP: CRM 2007 (For controls that support test mode enhancements. Requires SAP notes: 1147166, 1066565, and 1002944. Later SAP notes related to test mode enhancements are not supported.)

Java: IBM 32-bit JDK 1.5.x, SWT toolkit version 3.4

Java Add-in Extensibility: Eclipse IDE 3.4

.NET: .NET Framework 3.5Service Pack 1

For a complete list of all supported operating systems, browsers, and development environments, see System Requirements on page 9 and the HP QuickTest Professional 10.00 Product Availability Matrix.


8

EnhancementsAmong the feature enhancements included in the QuickTest 10.00 are:

Upgrade from QuickTest 9.5

Improved IntelliSense Functionality Added Control for Editing and Managing Actions in Automation Scripts

Improved Debugger Pane Design and Functionality

New Object Identification Solutions in Maintenance Run Mode

Additional Configuration Settings for Text Recognition Mechanism

New Look for Options, Settings, and File Dialog Boxes

QuickTest Toolbar Customization Options

Improved Web Add-in Extensibility

.NET Add-in and Extensibility Improvements

New Terminal Emulator Configuration Validation


System Requirements

Important: The information in this section is correct at the time of this release. Refer to the http://www.hp.com/go/QTP_SysReq page for the most updated supported system configurations.9

To successfully install and run QuickTest Professional, your computer must meet the following minimum system requirements:

Computer/Processor: PC with a Pentium III or higher (Pentium IV or higher recommended) microprocessor.

Operating System: Windows 2000 ProfessionalService Pack 4, Update Rollup 1 for Windows 2000 Professional Service Pack 4

Windows XP Professional 32-Bit EditionService Pack 2 or Service Pack 3

Windows XP Professional 64-Bit EditionService Pack 2

Windows Server 2003 32-Bit EditionService Pack 2

Windows Server 2003 64-Bit EditionService Pack 2

Windows Server 2003 R2 (32-Bit x86)

Windows Vista 32-bit Edition or Windows Vista 32-bit EditionService Pack 1

Windows Vista 64-bit Edition or Windows Vista 64-bit EditionService Pack 1

Windows Server 2008 32-Bit Edition

Windows Server 2008 64-Bit Edition

Note: The Quality Center client does not support 64-bit operating systems. Therefore, QuickTest-Quality Center integration functionality is not supported when working with 64-bit operating systems.

Memory: Minimum of 512 MB. Minimum 1 GB when using the Save movie to results option to capture movies during run sessions.

Color Settings: Minimum of High Color (16 bit).


10

Graphics Card: Graphics card with 4 MB video memory (8 MB and above recommended)

Free Hard Disk Space: 650 MB of free disk space for application files and folders, when only the default add-ins are installed. 800MB (recommended 1 GB) when all add-ins are installed.

You must also have an additional 120 MB of free disk space

on the system disk (the disk on which the operating system is installed). If you are not installing all of the QuickTest add-ins, less free disk space is required. The free disk space requirements do not include disk space required for any prerequisites that may need to be installed before installing QuickTest.

After QuickTest Professional is installed, it is recommended to have at least 150 MB free disk space on the system disk for the operating system and QuickTest Professional to run correctly.

Browser: To use QuickTest Professional, you must have one of the following Microsoft Internet Explorer versions installed on your computer.

Microsoft Internet Explorer 6.0 Service Pack 1

Microsoft Internet Explorer 7.0

Microsoft Internet Explorer 8.0 Beta 2

One of the above browsers must be installed to use QuickTest. For information on all browser versions supported for testing, see the HP QuickTest Professional 10.00 Product Availability Matrix.

Tip: To open the Product Availability Matrix document in a separate Adobe Reader window, either hold the CTRL key while clicking the above link or clear the option to Open cross-documents in same window in the Adobe Reader Preferences dialog box (Edit > Preferences).


Supported Environments and Programs

For a complete list of all supported environments and programs, see the HP QuickTest Professional 10.00 Product Availability Matrix.

Tip: To open the Product Availability Matrix document in a separate Adobe 11

Reader window, either hold the CTRL key while clicking the above link or clear the option to Open cross-documents in same window in the Adobe Reader Preferences dialog box (Edit > Preferences).

Important: The information in the linked document above is correct at the time of this release. Refer to the http://www.hp.com/go/QTP_SysReq page for the most updated supported environments and programs.

Additional Important InformationThis section provides supplemental information about the environments listed below. The information in this section should be used in conjunction with the data provided in the HP QuickTest Professional 10.00 Product Availability Matrix document referenced above.

HP Product Integrations on page 12

.NET Add-in on page 12

Oracle Add-in on page 13

Add-in for SAP Solutions on page 13

Siebel Add-in on page 13

Standard Windows Applications on page 13

Terminal Emulator Add-in on page 14

Visual Basic Add-in on page 14

Web Services Add-in on page 14


12

HP Product Integrations

For improved performance when running test sets remotely from the Quality Center Test Lab module, ensure that you are using the latest Quality Center patch.

.NET Add-in The QuickTest Professional .NET Add-in supports testing WPF controls inherited directly or indirectly from the System.Windows.Controls.Control class regardless of which language was used to create the application (for example, VisualBasic.NET, C#, and so forth), as well as third-party WPF controls that are inherited from the System.Windows.Controls.Control class and implement automation interfaces when the WPF Add-in is loaded.

The QuickTest Professional .NET Add-in supports:

Testing standard .NET Windows Forms controls from the System.Windows.Forms library.

Testing third-party .NET Windows Forms controls that are inherited from System.Windows.Forms.Control class.

In addition to the controls listed in the HP QuickTest Professional 10.00 Product Availability Matrix, custom-built QuickTest Professional support for a variety of Infragistics .NET Windows Forms controls is provided out-of-the-box by Infragistics TestAdvantage. For more information, refer to: http://www.infragistics.com/dotnet/testadvantageoverview.aspx#Overview

To view the full type name of a .NET Windows Forms object in your application, view the SwfTypeName identification property in the Object Spy.

You can also view a list of the base types of a selected object by running a statement using the following syntax:

MsgBox SwfTestObj(descr).GetROProperty("SwfTypeNames")

where SwfTestObj(descr) is the test object you want to check.

Running this statement causes a message box to open displaying the actual class at the top of the list and the base classes below it.


Oracle Add-in

The Oracle Forms and Oracle E-Business suite toolkits are supported only when working with Oracle JInitiator or Oracle Forms using the Sun Plug-in.

Add-in for SAP Solutions

Integration with SAP eCATT is not supported. To obtain a patch that 13

provides SAP eCATT support, contact HP Software Support.

CRM 2007 is supported only for controls that support test mode enhancements. Requires SAP notes: 1147166, 1066565, and 1002944. Later SAP notes related to test mode enhancements are not supported.

It is not recommended to work with other Web-based add-ins when the QuickTest Professional Add-in for SAP solutions is loaded. The Add-in for SAP solutions modifies certain Web configuration settings that may affect other add-ins or applications.

The SAP patch levels mentioned in the HP QuickTest Professional 10.00 Product Availability Matrix are the minimum supported levels. Except where otherwise indicated, later patch levels may be supported. If you want to test your SAP application using a later patch, contact HP Software Support to ensure that the QuickTest Professional Add-in for SAP solutions is compatible with your patch version.

Siebel Add-in

Siebel 7.7.x and later is supported only when the Siebel Test Automation module is installed and enabled. For information on installing and configuring Siebel Test Automation, refer to the Testing Siebel eBusiness Applications Guide, provided with your Siebel installation.

Standard Windows Applications

QuickTest Professional supports testing on applications based on Win32 API and MFC. QuickTest Professional does not support testing on 64-bit applications.


14

Terminal Emulator Add-in

If you are using a newer version of one of the emulators listed in the HP QuickTest Professional 10.00 Product Availability Matrix, or your emulator version is different from one listed in a minor version number only, select the nearest preconfigured version in the Terminal Emulator Configuration Wizard. It is likely that the QuickTest Professional Terminal Emulator Add-in

will work successfully with your emulator.

The QuickTest Professional Terminal Emulator Add-in can also be used with most other terminal emulators. You can define the exact configuration settings that you need using the Terminal Emulator Configuration Wizard.

For more information, see the HP QuickTest Professional Add-ins Guide.

Visual Basic Add-in

Note that Visual Basic .NET applications are supported by the QuickTest Professional .NET Add-in.

Web Services Add-in

A supported version of WS-I Interoperability Testing Tools is required for validating WSDL interoperability


HP Unified Functional Testing

With todays trend of application modernization, and the growing existence of composite applications, functional testing tasks span across GUI-based tests as well as service tests in order to verify a single business process.

The HP Unified Functional Testing package enables you to validate both the 15

GUI and headless elements in your application, enabling comprehensive testing of these complex business processes.

The Unified Functional Testing package includes HP QuickTest Professional and HP Service Test.

UFT (Unified Functional Testing) License: Terms of Use

When you purchase a UFT (Unified Functional Testing) license, you receive three separate license keys: Functional Testing Core, Functional Testing Add-ins, and Service Test.

When using a UFT concurrent license:

These three license keys must be installed on the same concurrent license server.

One UFT license permits the same user to use both a QuickTest Professional and Service Test license at the same time, but two different users must not use a QuickTest Professional and Service Test license at the same time.

You can monitor the licenses in use at any time using the WLMADMIN utility. For more information, see the HP Functional Testing Concurrent License Installation Guide.

When using a UFT seat license:

The three seat license keys provided for a single UFT seat license must be used by the same user.

For more information on Unified Functional Testing, contact your HP Quality Management supplier.


16

Useful Information

This section includes useful information about QuickTest Professional 10.00 (sub-divided according to add-in).

GeneralUseful Information on page 16

.NETUseful Information on page 22 OracleUseful Information on page 24

PeopleSoftUseful Information on page 24

SAPUseful Information on page 25

SiebelUseful Information on page 26

StingrayUseful Information on page 28

Terminal EmulatorsUseful Information on page 30

WebUseful Information on page 30

GeneralUseful Information

If you are upgrading to QuickTest Professional 10.00 from QuickTest Professional 9.5, you can upgrade without uninstalling QuickTest. (Run the installation. The Setup program automatically detects QuickTest 9.5 and offers to upgrade it to QuickTest 10.00.)

If you are upgrading to QuickTest Professional 10.00 from QuickTest Professional 9.2 or earlier, you need to first uninstall your previous version of QuickTest Professional and the Quality Center Add-in (if relevant).

You must be logged on with administrator privileges to install or uninstall QuickTest Professional.


When upgrading from QuickTest Professional 9.2 or earlier, you can use the Save and Restore Settings utility to save some existing customization settings and registry keys before you uninstall the old QuickTest version, and then restore them after you install a new version.

The Save and Restore Settings utility is particularly useful for saving the manual customizations made to extensibility and Web event configuration 17

.xml files.

For more information, open the Save and Restore Settings utility from the root of the QuickTest installation DVD and click the Help button.

To use QuickTest Professionals debugging capabilities, you must install the Microsoft Script Debugger. You can install the Script Debugger:

At the end of the QuickTest Professional setup.

Using the Add/Remove Windows Components option in the Add/Remove Programs window.

Using the Additional Installation Requirements tool, available from the QuickTest Professional program folder (Start > Programs > QuickTest Professional > Tools > Additional Installation Requirements).

By downloading it later from Microsofts Windows Script Technologies site: http://www.microsoft.com/downloads/details.aspx?FamilyID=2f465be0-94fd-4569-b3c4-dffdf19ccd99&DisplayLang=en

If you are using concurrent licenses with QuickTest Professional 10.00, you must work with version 9.0 or later of the HP (Mercury) Functional Testing Concurrent License Server. QuickTest Professional 10.00 is not compatible with earlier versions of the HP Functional Testing Concurrent License Server.


18

Text Recognition for Windows-Based Environments

You can use the text and text area checkpoint or output value commands to verify or retrieve text from your Windows-based objects. Alternatively, you can use the testobject.GetText (for Terminal Emulator objects), testobject.GetVisibleText, or testobject.GetTextLocation test object methods, or the TextUtil.GetText or TextUtil.GetTextLocation reserved object methods

to capture the text you need.

When capturing text for a text/text area checkpoint or output value step, or using one of the above mentioned methods, QuickTest captures the text either directly from the object using a Windows API-based mechanism (default mechanism) or using an OCR (optical character recognition) mechanism provided by ABBYY Software Ltd, based on the settings in the General > Text Recognition pane of the Options dialog box.

You can also set text recognition behaviors by modifying the values in the following registry key: HKEY_CURRENT_USER\SOFTWARE\Mercury Interactive\QuickTest Professional\MicTest\OcrEngine

Important: The Windows Registry Editor is an advanced tool for changing settings in your system registry. You should not edit your registry unless absolutely necessary. If there is an error in your registry, your computer may not function properly.


The following table lists the possible value entries for the OcrEngine key.

Name Possible Values

maxHforSingleBlock and maxWforSingleBlock

Indicates the height or width of a single text block in pixels, for example, 29. Modify both value entries to instruct the OCR mechanism to treat the object as a 19

single text block.

Default for both = 0 (indicates that multiple text block should be used because the maximum pixel height and width for a single block is not defined.)

Tips:

Sometimes, text on small objects or in a small text area is not captured (or is captured incorrectly). In cases such as these, specifying the maximum text area size in pixels may help improve text recognition. This causes the OCR mechanism to focus on a specific area and treat it as a single text block (and not as multiple text blocks, as it would normally do).

You can use QuickTests Object Spy to find the height and width of the object.

Note: You can also control whether QuickTest uses Single text block mode or Multiple text block mode from within QuickTest by selecting Tools > Options > General node > Text Recognition node, and then selecting the relevant option.


20

mode 0 - No OCR. Instructs QuickTest to use only the Windows API-based mechanism (and not the OCR mechanism) to retrieve text from the object.

1 - Windows API/OCR. Instructs QuickTest to first try to retrieve text directly from the object using the Windows

Name Possible ValuesAPI-based mechanism. If no text can be retrieved, QuickTest tries to retrieve text using the OCR mechanism. (Default) (Highly recommended when working with CJK languages.)

2 - OCR/Windows API. Instructs QuickTest to first try to retrieve text from the object using the OCR mechanism. If no text can be retrieved, then QuickTest uses its Windows API-based mechanism to retrieve text from the object.

3 - OCR only. Instructs QuickTest to use only the OCR mechanism (and not the Windows API-based mechanism) to retrieve text from the object. (Required when working with Windows Vista.)

Note: You can also set the text recognition mode in QuickTest by selecting Tools > Options > General node > Text Recognition node, and then selecting the relevant Use text recognition methods in this order option.


supportedLanguages Indicates the language dictionaries that the OCR mechanism uses when retrieving text from the object.

Enter a comma to separate the languages, for example: English,German,Spanish,French

Name Possible Values21

Note: Although these text-capturing options and methods are available for Windows-based objects, keep in mind that any text-recognition mechanism may occasionally capture unwanted text information (such as hidden text and shadowed text), or may misinterpret the text content.

Additionally, text-capturing steps may behave differently in different run sessions depending on the operating system version you are using, the installed service packs, other installed toolkits, the APIs used in your application, and so on.

Therefore, when possible, it is highly recommended to check text from your application window by inserting a standard checkpoint, output value, or GetROProperty method for the object containing the desired text to retrieve the value of its text (or similar) property.

Notes:

Combined hieroglyphic languages (CJK - Chinese, Japanese, or Korean) and non-hieroglyphic languages are not supported. For example, you cannot specify: English,Japanese

Support is provided for only one hieroglyphic language at a time.

You can also specify the supported languages from within QuickTest by selecting Tools > Options > General node > Text Recognition node, and then selecting the languages from the Available languages list to include in the Supported languages.


22

For more information, see the relevant sections in the HP QuickTest Professional User Guide, and search for the GetText, GetVisibleText, and GetTextLocation methods in the relevant sections of the QuickTest Object Model Reference Help.

See also the limitations in the section: Text Recognition Support for Windows-Based Environments on page 86. .NETUseful Information

Do not load the .NET Add-in if you are using the Oracle Add-in to test Oracle applications.

.NET Web Forms support does not work correctly when the SAP or Siebel add-ins are loaded. Do not load SAP and Siebel Add-ins when using the .NET Add-in to test Web Forms controls.

You can use the .Object property to access all properties and methods of WPF, .NET Windows Forms and .NET Web Forms objects.

For the most common UI controls, context-sensitive support is also available.

The SwfTable.SetCellData method is recorded only after you move the focus from the edited cell to another cell.

Testing Applications that Use Microsoft .NET Framework 1.0

An application may use components that are built on different versions of the Microsoft .NET Framework. The default behavior of CLR version 1.1 and later is to unify usage of framework assemblies. The runtime version that is associated with an application determines which version of the Microsoft .NET Framework assemblies are used by the application and all of its components.

For example, if an application is associated with version 1.1 of the Microsoft .NET Framework and uses the System.Data assembly, then version 1.1 of the System.Data assembly is loaded and shared across all components used by the application. If an application component refers to version 1.0 of the System.Data assembly, the reference is promoted at runtime to reference version 1.1.


The Microsoft .NET Framework 1.0 does not perform unification by default. As a result, an application that uses components built with different Microsoft .NET frameworks may load different versions of the same assembly at runtime.

If you want to test applications that use NET Framework 1.0, you must apply binding redirection of framework assemblies (for version 1.0 only) at the 23

machine level, as described below. Note that until you make the required configuration changes, testing applications based on the .NET Framework 1.0 may cause unexpected results.

To manually update the Microsoft .NET Framework 1.0 configuration after installing the .NET add-in:

1 Log in to your computer with administrator permissions.

2 Open a Command Prompt (Start > Programs > Accessories > Command Prompt).

3 Type cd /d \bin and press ENTER to change the path to the QuickTest Professional bin folder.

4 Type NetUpdateConfig /config and press ENTER.

This command performs the required changes in the machine.config file under the Microsoft .NET Framework 1.0 installation. The original file is saved as machine.config.bak.

For additional information, refer to: http://msdn2.microsoft.com/en-us/library/db7849ey(vs.71).aspx


24

OracleUseful Information

The QuickTest Professional Oracle Add-in supports working with Java clients (not Windows clients).

Do not load the .NET Add-in if you are using the Oracle Add-in to test Oracle applications. The Oracle Applications server provides a unique Name attribute for many application objects. QuickTest can use this attribute to identify objects. This improves the reliability of the test object description and usually prevents the need for learning the ordinal identifier, which may change between the time you record and run a test.

For more information on using the Name attribute in test object descriptions, see the HP QuickTest Professional Add-ins Guide.

PeopleSoftUseful Information

Avoid recording and running tests on Web applications while the PeopleSoft Add-in is loaded.

The PeopleSoft Add-in is not compatible with the QuickTest Professional Add-in for SAP Solutions or the QuickTest Professional Siebel Add-in. Do not load either of these add-ins when loading the PeopleSoft Add-in.


SAPUseful Information

QuickTest provides the SAP.txt function library, which extends the testing capabilities on SAP Gui for Windows applications and makes it easier to write keyword-driven SAP steps, especially for business components. This function library is available locally in \dat\BPT Resources and is automatically uploaded and stored in 25

your Quality Center project when you connect to it. For more information on business process testing, see the HP Business Process Testing User Guide.

In the Windows Applications tab of the Record and Run Settings dialog box, select Record and run on these applications (opened when a session begins) and confirm that the list of Windows applications is empty. These settings prevent you from inadvertently recording operations performed on Windows applications (such as e-mail) during your recording session and prevents QuickTest from opening unnecessary applications when you record or run tests on SAP applications.

The PeopleSoft Add-in is not compatible with the QuickTest Professional Add-in for SAP Solutions or the QuickTest Professional Siebel Add-in. Do not load either of these add-ins when loading the PeopleSoft Add-in.


Testing SAP Gui for Windows Applications

Consider the tips and guidelines below when testing SAP Gui for Windows applications.

Testing SAP Gui for Windows applications is performed using the SAP Gui scripting API. This API is supported in specific environments. For more information, visit www.sap.com.

Before you begin to design tests on your SAP Gui for Windows application, confirm that you have properly configured your SAP server and client including:

Check the package and patch versions installed on the application server and the client.

Enable the Scripting Interface on the SAP Application Server and on the SAP Gui for Windows client.


26

Set the SAP Client F4 Help Settings to use the proper display mode.

Confirm that the Low speed connection option is not selected for the server to which you are connecting.

For more information on these configuration settings, see the HP QuickTest Professional Add-ins Guide. The steps that QuickTest records are based on the events sent by the SAP Scripting API. Therefore, although QuickTest records a step for each operation you perform, it adds the steps to your test only when API events are sent to QuickTest (when information is sent to the SAP server). You may also see steps in your test that do not directly correspond to an operation you performed, or an operation you performed may be shown as two or more steps in your test. For more information on the SAP Scripting API events, refer to your SAP documentation.

The SAPGuiSession test object contains information about the current session. All the information displayed in the status bar (system name, system number, current transaction, username, and so forth) can be verified by creating a checkpoint on the SAPGuiSession test object in your test.

SiebelUseful Information The information in this section applies to the Siebel Add-in in general (for all Siebel versions).

For optimal performance, it is strongly recommended that when testing Siebel applications, you work with only the Siebel Add-in loaded. Note that the QuickTest Professional Web Add-in does not need to be loaded to use the Siebel Add-in.

It is strongly recommended that when testing Web applications that do not contain Siebel objects, you do not load the Siebel Add-in.

When the Siebel Add-in is loaded, the object identification definitions for both Web and Siebel objects are set automatically and you cannot access the object identification definitions for Web or Siebel objects (even if the Web Add-in is also loaded).

Tests or components recorded on Siebel versions earlier than Siebel 7.7.x cannot be run on Siebel 7.7.x applications. Tests or components recorded on Siebel 7.7.x applications cannot be run on earlier Siebel versions.


It is recommended to use the same Browser settings for the Java Virtual Machine while recording and running tests and components created with the Siebel add-in. This is because applets are represented differently when using the Sun Plug-in and the Microsoft Java Virtual Machine.

The PeopleSoft Add-in is not compatible with the QuickTest Professional Add-in for SAP Solutions or the QuickTest Professional Siebel Add-in. Do not 27

load either of these add-ins when loading the PeopleSoft Add-in.


Information for Siebel 7.7.x and Later

The information in this section is relevant only when using the QuickTest Siebel Add-in with Siebel 7.7.x and later applications.

To test Siebel 7.7.x and later applications, you must ensure that your Siebel server has the Siebel Test Automation module installed and correctly configured. For detailed information, see the Testing Siebel eBusiness Applications Guide, provided with your Siebel installation.

To load Siebel Test Automation, additional URL parameters must be specified. For more information, see the Testing Siebel eBusiness Applications Guide, available with your Siebel installation.

If you select the Open the following application when a record or run session begins option in the Siebel tab of the Record and Run Settings dialog box, QuickTest adds the required parameter values automatically. If you select the Record and run test on any open browser option, you must specify the required parameter values as part of the application URL.

If a Session timeout error occurs in your Siebel application, the login parameters are not saved. After you log out and log in again, you must navigate to the correct URL that contains the required parameter values.

Three new properties are added to each Web and SblXXX test object when the Siebel Add-in is loadedRepositoryName, UIName, and SiebelObjType. The property values may be empty for some of the objects.


28

StingrayUseful Information

QuickTest support for Stingray objects is based on an agent entity in the Stingray application that interacts with QuickTest to enable recording and running operations. There are two different modes for establishing this agent entity.

Run-time Agent Mode: QuickTest injects an agent dll into the

application's process during run-time. This is the recommended mode.

Precompiled Agent Mode: You make slight modifications to the application source code, referring to predefined agent files that will be added to the application project. Use this mode only if your Stingray application uses statically linked MFC libraries.

You set up support for Stingray objects using the Stingray Support Configuration Wizard. When you select to install the Stingray Add-in in the QuickTest Professional installation, then you are prompted to run the Stingray Support Configuration Wizard in the Additional Installation Requirements screen at the end of the installation process. The wizard walks you through the steps that are necessary to configure QuickTest to work according to the agent mode that you select and according to the versions of Stingray libraries in your application(s). If the wizard detects problems during the configuration procedure, note the warnings that are issued.

To reconfigure QuickTest Stingray support at a later time, for example, for different Stingray application versions, launch the wizard by selecting it from the QuickTest program group, or, in QuickTest, from the Stingray pane in the Options dialog box (Tools > Options).


Note for WinRunner Stingray Add-in users working in run-time agent mode: The version of the Stingray agent installed with the WinRunner Stingray Add-in may be different than the version of the Stingray agent installed with the QuickTest Professional Stingray Add-in. By default, if you load the WinRunner Stingray Add-in while QuickTest Professional is 29

runningwith or without the add-in loadedunexpected QuickTest behavior can occur. (There is no restriction on having both add-ins installed on the same computer.)

If you want to work with the WinRunner Stingray Add-in and QuickTest simultaneously, for example, if you want to call a QuickTest test containing Stingray objects from WinRunner or vice versa, you must first ensure that WinRunner and QuickTest are both using the latest version of the Stingray agent. To do this, search for the Stgagent.dll file in \bin\StingrayAgent\AgentDll\MFC\OG


30

Terminal EmulatorsUseful Information

To ensure that QuickTest and your terminal emulator integrate successfully while recording a test or component, open and connect your terminal emulator session before recording begins. While running tests or components, you can add a SystemUtil.Run statement to the beginning of your test or component to automatically launch your emulator session from

QuickTest. For more information, see the Utility Objects section of the HP QuickTest Professional Object Model Reference.

If your terminal emulator has an option to automatically resize the terminal emulator window according to the font size, then it should be enabled. For example, in the EXTRA! 6.7 emulator, select Settings > Font > Autosize window to font size.

You can run tests or components using the QuickTest Professional Terminal Emulator Add-in from other HP products, for example, Quality Center. Before you run these tests or components, make sure you select the required emulator on the computer on which the test or component is to run, using the QuickTest Tools > Options >Terminal Emulator pane.

WebUseful Information

Avoid recording and running tests on Web applications while the PeopleSoft Add-in is loaded.


Notes and Limitations

This section includes information and limitations about QuickTest Professional 10.00 in the product areas listed below. (The product areas are sub-divided according to add-in where relevant.)

General Issues on page 3231

Installation, Licensing, and Configuration on page 41

Creating, Editing, and Running Testing Documents on page 46

Quality Center Integration and Business Process Testing on page 80

Working with Microsoft Windows Vista and Windows Server 2008 on page 84

Text Recognition Support for Windows-Based Environments on page 86

Active Screen on page 87

Automation on page 88

Data Table on page 89

Checkpoints and Output Values on page 89

Object Repository on page 96

HP Screen Recorder on page 96

QuickTest Professional Documentation on page 97

LoadRunner and Business Process Monitor Integration on page 98


32

General Issues This section includes the following:

QuickTestGeneral Issues on page 32

JavaGeneral Issues on page 33 OracleGeneral Issues on page 36

PeopleSoftGeneral Issues on page 37

WPFGeneral Issues on page 37

.NET Windows FormsGeneral Issues on page 37

.NET Web FormsGeneral Issues on page 39

StingrayGeneral Issues on page 40

WebGeneral Issues on page 40

QuickTestGeneral Issues

QuickTest does not support hidden files. If you mark a QuickTest test, folder, or other QuickTest file as hidden (by selecting the Hidden attribute in the folder or file properties dialog box in Windows Explorer), QuickTest may behave unexpectedly.


JavaGeneral Issues

You load Java Add-in extensibility support by selecting a child add-in under Java in the Add-in Manager. If you load support that was developed using a Java Add-in Extensibility SDK version earlier than version 10.00, then when you open one of the QuickTest dialog boxes that display test object classes for a selected environment (such as the Object Identification dialog box), 33

the extensibility test object classes are displayed in the wrong list. If you select the child add-in in the Environment list, the list of test object classes is empty. Instead, the extensibility test object classes are displayed directly under the Java environment instead of being displayed under the child add-in in the Environment list.

Additionally, in some cases, the Generate Script button in the Object Identification dialog box does not function properly.

Workaround:

a Locate the test object configuration file associated with the child add-in: \dat\Extensibility\Java\TestObjects.xml.

(If working with Quality Center: \dat\Extensibility\Java\TestObjects.xml.)

b In the XML file, locate the PackageName attribute in the TypeInformation element, and change its value from JavaPackage to the name of the child add-in.

c Save the file and reopen QuickTest.

d If this extensibility support (child add-in) was developed by a third party, you may want to contact them for assistance.

If, while recording keyboard operations in a JFC single-line edit box in an IME composition window, you press the ENTER key to select the composition string, the key press may be recorded as the Activate method, thereby generating an extra step. For example: JavaWindow("Application").JavaEdit("User Name").ActivateThis extra step generally does not affect the run session adversely.

Workaround: Before running your test or component, remove the extra step that was recorded.


34

Adding a -Xincgc flag to the java.exe command line (in the Record and Run Settings dialog box or in a batch file) prevents the Java support from working properly.

Workaround: When testing with QuickTest Java support, do not use -Xincgc in your command line, or, alternatively, do not use the dynamic transformation support mechanism. For more information, see the

HP QuickTest Professional Add-ins Guide.

The PropertyValue argument (second argument) of the WaitProperty method for any Java test object can be only of type string.

Workaround: Use a string instead of the original type. For example, instead of 1, use "1". For example: y = JavaCheckBox("Active").WaitProperty ("enabled", "1", 1000)

By default, moving and resizing of Java windows are not recorded. This is because it may cause redundant recordings in some cases.

Workaround: To instruct the Java Add-in record these actions, use the Setting.Java method to set the record_win_ops variable to 1. For example: Setting.Java("RECORD_WIN_OPS") = 1

AWT popup menus are recorded by the Standard Window control support WinMenu test object (while other Java menus are recorded using the JavaMenu test object). You cannot perform checkpoints or Active Screen operations on such menus.

Workaround: Use other verification methods (such as using GetTOProperty). For more details on verification methods, see the HP QuickTest Professional User Guide.

When selecting a JAR file from the command line in the Record and Run Settings dialog box, you should manually add -jar to the Command line box before you invoke the Java application.

If you intend to launch your Java application using the Record and Run Settings dialog box without using a batch file (or another executable file), and without the -jar command line option (after selecting a JAR file), you should include the fully qualified name of the Java class in the Command line box.

A call to .Object.startModal of a JavaInternalFrame or JavaDialog object may cause QuickTest to behave unexpectedly until the dialog box is closed.


The use of multibyte characters in a multiline edit field object is not supported.

For button objects (either JavaButton or a button in a JavaToolbar) whose label is determined by the name of the image file they display, the process of naming the test object when running in JDK 1.6 is different than the one used when running in JDK 1.5. 35

Therefore, if you have a test or component containing button objects that were learned on JDK 1.5 and labeled according to their image file, when you run it on JDK 1.6, the test or component may fail.

Workaround:

For a JavaButton objectrelearn the object on JDK 1.6. Then modify the test to use the new test object, or delete the old object from the object repository and rename the new test object to match the object name used in the step. (Make sure the Automatically update test and components steps when you rename test objects option is selected in the General pane of the Options dialog box.)

For a button in a JavaToolbar objectmodify the Item argument in the JavaToolbar statement to refer to the relevant button. You can specify the buttons index, or you can use the Object Spy to spy on the toolbar button, and then provide the label identification property as the Item argument.

The ALT+F4 keyboard shortcut (used for closing a Java applet or Java application) is not supported for recording or running.

Workaround: Use a Close menu command or button to close a Java applet or Java application during a recording session. Alternatively, manually add a JavaWindow(...).Close step.


36

OracleGeneral Issues

OracleListOfValues.Select always selects the first item when there are multiple items with identical values in the first column.

Workaround: To select an item other than the first one, specify the items index value instead of a string as the argument value. The hierarchy of a tab inside of another tab is not recorded correctly. This stops auto-tab selection from working on such hierarchies during a run session.

Workaround: Add an OracleTabbedRegion.Select method for the appropriate tab before any step that performs an operation on an object inside a tab that is inside another tab.

The Log out of the application when the test closes option in the Record and Run Settings dialog box does not work if the Responsibilities List of Values window is displayed in the Oracle Applications session.

During a run session, an OracleCalendar.Enter step may sometimes enter a value in the wrong field.

Workaround: Use an OracleTextField.Enter step to enter the value in the date field instead.

Active Screen captures are not supported for OracleListOfValues and OracleNotification test objects.

Test objects that require the index property for their description (for example, range flexfield objects) cannot be created from the Active Screen.

Workaround: Use the Add Objects button in the Object Repository dialog box to add these test objects directly from your Oracle Applications instead.

The recovery scenario pop-up window trigger event is not supported when testing Oracle Applications.

Running a test or component on an Oracle Applications session that was created by refreshing the browser is not supported.

Simultaneous testing of multiple Oracle Applications sessions is not supported.

The use of multibyte characters in a multiline edit field object is not supported.


PeopleSoftGeneral Issues

The Active Screen may not function correctly when working with non-English UI servers.

If you use the ENTER key to activate a search operation while recording a test, QuickTest may not perform the operation as expected during the test run.37

Workaround: Activate the search by clicking the Search button with the mouse.

The use of keyboard shortcut keys to perform operations while recording is not supported.

WPFGeneral Issues

When you spy on a WPF object using the Object Spy (or the .NET Windows Forms Spy when the .NET Add-in is loaded), and the Record and Run Settings dialog box is not configured to record on the WPF application on which you are spying, QuickTest recognizes the object as a standard Windows object.

Workaround: Close your WPF application. In QuickTest, open the Record and Run Settings dialog box (Automation > Record and Run Settings) and in the Windows Application tab, select the Record and run test on any Windows application option. Reopen your WPF application and then spy on it again.

.NET Windows FormsGeneral Issues

Applications containing numerous controls might have performance problems while recording.

Workaround: Change the Active Screen capture level to Partial or Minimum to capture less information. To do this, select the Tools > Options > Active Screen node and modify the setting.

Navigating in grid controls using keyboard keys (for example, to select cells, rows, and so on) may not be recorded correctly.

Workaround: Use the mouse to navigate in the grid control.

If you call the Back method for a Microsoft DataGrid control on a table that does not have a parent row, no operation is performed when the statement runs, and no error message is displayed.


38

Grid controls in the Card View mode are not supported.

Changing the format of a DateTimePicker control during a test run or between record and run sessions (for example, from "Long Date" to "Time") will cause the test run to fail.

Combo box objects of style Simple Combobox are not supported. If a window in the tested application has an opacity property value not equal to 100% (that is, the form is completely or partially transparent), the Active Screen captures the image displayed below the form, and not the transparent window.

Tests recorded with .NET Framework 1.0 or 1.1 on Microsoft PropertyGrid control (and perhaps other compound controls that use Toolbar as an internal element) may stop working when executed with .NET Framework 2.0. This occurs because in .NET Framework 2.0, the Toolbar control on top of the PropertyGrid control was replaced by ToolStrip and MenuStrip controls.

Workaround: Update the description of the appropriate SwfToolBar test object with the correct SwfTypeName identification property value.

If you edit your test or component in the Keyword View or Expert View while recording, some test object methods are unavailable for selection in the Keyword View and are not displayed in the Expert View IntelliSense. In addition, the F1 (Help) key may work incorrectly for some methods while recording.

Workaround: Stop recording before editing your test or component or using the F1 key.

Operations on a grid cell that was selected before you started recording on the grid control may be recorded incorrectly. For example, a child cell element operation may be recorded instead of the parent grid operation (for example, SetCellData).

Workaround: Before performing operations on a cell that is already selected, begin recording, move the focus to another cell, select the required cell, and then perform the required operation.


.NET Web FormsGeneral Issues

Tests on WbfTreeView test objects that contain special characters may not run as expected.

Workaround: To run a test on a WbfTreeView item that contains special characters, use the #index format. See the .NET Web Forms Object Model Reference Help for details.39

WbfTreeView, WbfToolbar, and WbfTabStrip test objects are not supported for browser control applications.

Active Screen operations are not supported for WbfTreeView, WbfToolbar, and WbfTabStrip objects.

Performing a Select or Expand operation on a WbfTreeView object that causes page navigation may fail due to a synchronization problem.

Workaround: Try running the test on the WbfTreeView object step-by-step, meaning instead of using WbfTreeView.Select "item1;item2;item3;"Use WbfTreeView.Expand "item1"WbfTreeView.Expand "item1;item2"WbfTreeView.Select "item1;item2;item3;"

Working on a .NET Web Forms application that has calendars with more than one unified style is not fully supported.

The value of the Selected Date and Selected Range identification properties is always none for WbfCalendar objects in selection mode none.

To retrieve correct values for WbfCalendar Selected Date and Selected Range identification properties, the selected date or range must be currently visible in your Web Forms application.

All operations on grouping areas in WbfUltraGrid objects (Infragistics UltraWebGrid) are not recorded.

Operations performed in a rapid sequence on WbfUltraGrid objects may not be recorded.

Workaround: Try to limit the recording to 1-2 operations per second.

WbfUltraGrid column names are comprised of the inner HTML of the column header, and therefore may include extraneous information.


40

WbfUltraGrid may fail to sort columns in a descending order when the column is not already sorted.

Workaround: Split the Sort call into two callsfirst sort in ascending order, then sort in descending order. For example:

Change:WbfUltraGrid("UltraWebGrid1").Sort "Model","Descending"

To:

WbfUltraGrid("UltraWebGrid1").Sort "Model","Ascending"WbfUltraGrid("UltraWebGrid1").Sort "Model","Descending"

StingrayGeneral Issues

Applying Stingray Support Configuration settings to all users on the computer has no effect on users that have opened QuickTest at least once.

Workaround: Apply Stingray Support Configuration settings separately for each user that has opened QuickTest at least once.

QuickTest does not support both Unicode and non-Unicode in the same application when the Stingray Add-in is loaded.

WebGeneral Issues

Testing on Microsoft Internet Explorer 8.0 Beta 2 is supported on Windows XP and 2003 only.

QuickTest does not support the showModalDialog command in Mozilla Firefox.

QuickTest does not support anonymous content elements in non-XUL frames. (For example, the buttons in the Mozilla Firefox SSL exception page.)


Installation, Licensing, and ConfigurationThis section includes the following:

QuickTest ProfessionalInstallation Issues on page 41

Java Add-inInstallation Issues on page 4341

Oracle Add-inInstallation Issues on page 44

Terminal Emulator Add-inInstallation Issues on page 45

QuickTest ProfessionalInstallation Issues

As documented in the HP QuickTest Professional Installation Guide, seat licenses are not supported on Windows 2008 server. However, the license installation wizard does not disable the option to select Seat license on this operating system. If you do select it, the license key installation will fail.

When you connect to a Vista or Windows XP 64-bit operating system using a Remote Desktop Connection, you cannot select to install a seat license or modify the QuickTest license type from Concurrent to Seat.

Workaround: Open QuickTest on the physical computer to change the license type, or connect to the computer using a console that does not create a session when it accesses the remote computer.

As documented in the HP QuickTest Professional Installation Guide, when upgrading a QuickTest Professional 9.5 installation using a silent installation, you must use the TARGETDIR parameter in your command line to ensure that the upgraded installation uses the same folder as the existing QuickTest 9.5.

If you fail to use the TARGETDIR parameter in your command line and QuickTest Professional 9.5 was installed in a folder other than the default QuickTest installation folder, your previous QuickTest configurations will not be saved and QuickTest may not behave as expected, even if the installation appears to run successfully. For more information on installing QuickTest silently, see the HP QuickTest Professional Installation Guide.

The path in which installation files for QuickTest Professional are located, and the path in which QuickTest Professional is installed, can contain only English characters.


42

The HP Functional Testing Concurrent License Server does not support the use of Network Address Translation (NAT).

You cannot install QuickTest Professional with a demo license over a previous version of QuickTest Professional whose demo license has expired and a regular license was never installed for it.

If the LSHOST variable was set to a server on another domain, the server

utility lsmon.exe might behave unexpectedly.

The concurrent license does not include a demo license and does not work without an HP Functional Testing Concurrent License Server and an installed license key.

You cannot change the license type from seat to concurrent or vice versa when logged into the machine without administrator privileges.

Workaround: To change the license type, log into the machine as a user with administrator privileges.

Uninstalling the QuickTest Professional Floating License Server version 6.0 may cause QuickTest to fail to retrieve a license during startup.

Workaround: Back up the lservrc file before uninstalling the QuickTest Professional Floating License Server version 6.0, and then copy the file to the new installation path or reinstall the license strings after installing the license server.

If version 6.0.0.8169 of Pdm.dll is found on your computer, the setup program will recognize this during the QuickTest Professional installation and will instruct you to download the corrected DLL from the Microsoft site. For more information, see http://support.microsoft.com/kb/q293623/.

Installing QuickTest Professional on a network drive is not supported.

When working with a terminal server (for example, Windows 2003 server), you must connect to QuickTest using a concurrent license. Seat and demo licenses are not supported on terminal servers.

Workaround: Install a concurrent license server on the terminal server and then connect to it, or connect to a concurrent license server that is installed on a different computer.


When uninstalling QuickTest Professional in Windows 2003, the uninstall program may stop responding in the "removing backup files" stage.

Workaround: End the msiexec.exe and Ikernel.exe processes from the Windows Task Manager and restart your computer. If this problem occurs during the installation process, end the msiexec.exe and Ikernel.exe processes from the Windows Task Manager and re-run the Setup 43

(installation) program.

When uninstalling QuickTest Professional in Windows 2003, the uninstall program may not complete successfully, indicating that the uninstall process could not be completed and QuickTest Professional should be uninstalled manually. This behavior occurs due to a bug that was introduced in InstallShield Developer 8.02. For more details, see http://support.installshield.com/kb/view.asp?articleid=Q111000.

Workaround: After performing an uninstall, manually delete any files that remain in the QuickTest Professional installation folder.

If you have QuickTest Professional 6.5.x add-ins that were installed directly on QuickTest Professional 8.0.x or later (and were not installed previously on QuickTest Professional 6.5.x), the uninstall program does not uninstall these add-ins.

Workaround: After performing an uninstall, manually delete any files that remain in the QuickTest Professional installation folder.

Java Add-inInstallation Issues

To work with WinRunner Java/Oracle Add-in 7.6, the dual agent patch (located in the WR76DualAgentPatch folder of the installation DVD) needs to be installed.

Note: Install the WR76DualAgentPatch patch only after you install the QuickTest Professional Java Add-in.


44

In Windows XP and Windows 2003, after you install the QuickTest Professional Java Add-in, the Windows Remote Shell Service (rshsvc.exe) may fail and display an error message every time you restart the computer. This occurs only if the Remote Shell Service is configured to run automatically.

Workaround: Either disable the automatic launching of the Remote Shell

Service, or move the following variables from the System Variables section of the Environment Variables dialog box to the User Variables section: _classload_hook, _JAVA_OPTIONS, IBM_JAVA_OPTIONS, and MSJAVA _ENABLE _MONITORS.

Oracle Add-inInstallation Issues

To work with WinRunner Java/Oracle Add-in 7.6, the dual agent patch (located in the WR76DualAgentPatch folder of the installation DVD) needs to be installed.

If you install an Oracle JInitiator 1.1.x version after you install the QuickTest Professional Oracle Add-in, you must repair QuickTest to test applications running in the newly installed JInitiator version. For more information, see the HP QuickTest Professional Add-ins Guide.

Note: It is not necessary to re-install or otherwise configure the QuickTest Professional Oracle Add-in if you installed a new Oracle environment other than JInitiator 1.1.x.

In Windows XP and Windows 2003, after you install the Oracle Add-in, the Windows Remote Shell Service (rshsvc.exe) may fail and display an error message every time you restart the computer. This occurs only if the Remote Shell Service is configured to run automatically.

Workaround: Either disable the automatic launching of the Remote Shell Service, or move the following variables from the System Variables section of the Environment Variables dialog box to the User Variables section: _classload_hook, _JAVA_OPTIONS, IBM_JAVA_OPTIONS, and MSJAVA _ENABLE _MONITORS.


Terminal Emulator Add-inInstallation Issues

If the QuickTest Professional Terminal Emulator Add-in is installed and loaded, but there is no terminal emulator installed on your computer, the following error message is displayed: QuickTest Terminal Emulator support is not configured correctly. Either the terminal emulator is not installed on your computer or the HLLAPI DLL was not found.45

Workaround: When you open QuickTest, clear the Terminal Emulators check box in the Add-in Manager.

Note: You can prevent this message from appearing by adjusting your emulators configuration settings. For more information, see the HP QuickTest Professional Add-ins Guide.

When working with an emulator that does not support HLLAPI, or with an emulator that has been configured as supporting text-only HLLAPI operations, do not change the size of the terminal emulator window after configuring the emulator settings.

When installing a Hummingbird HostExplorer terminal emulator or patches, make sure that QuickTest Professional is closed.

To enable support for a NetManage Web-To-Host Java Client session that is configured to open in a separate window, specify the title of your session window using the Tools > Options > Terminal Emulator > Adjust Configuration > Object identification settings > Identify emulator window based on title bar prefix option.

Tip: You may need to clear this value when switching to another configuration.

When using the Terminal Emulator Configuration Wizard to configure the screen sizes of NetManage RUMBA Web-to-Host, you cannot use the Mark Text Area option to draw on top of the emulator window.

Workaround: Configure the text area position of the screen manually.


46

Creating, Editing, and Running Testing DocumentsThis section includes the following:

General Issues on page 47

ActiveX-related Issues on page 53 Delphi- and Delphi Add-in Extensibility-related Issues on page 54

Java-related Issues on page 55

.NET Web Forms-related Issues on page 56

Oracle Applications-related Issues on page 56

PowerBuilder-related Issues on page 57

SAPTesting Windows-based SAP Application on page 57

SAPTesting Web-based SAP Applications on page 61

Siebel 7.7.x and LaterCreating and Running Tests and Components on page 62

Siebel 7.0.x and 7.5.xCreating and Running Tests and Components on page 63

Standard Windows ObjectsCreating and Running Tests and Components on page 66

Stingray ApplicationsCreating and Running Tests and Components on page 67

Terminal EmulatorsRecording and Running Tests and Components on page 69

Visual Basic ApplicationsCreating and Running Tests and Components on page 74

Web ObjectsCreating and Running Tests and Components on page 74

Web ServicesCreating Tests and Components on page 79


General Issues

QuickTest cannot record or run steps if it has limited access to the processes of the application you are testing.

Workarounds:

Make sure that the application you are testing is started by the same 47

Windows user as QuickTest.

Make sure that neither you nor the tested application actively prevent QuickTest from accessing the applications processes.

If you export a large run results report to DOC format, it may take a long time to open the document in Microsoft Word XP or 2003. (The problem does not occur when opening the report in Microsoft Word 2007.)

Using the LoadAndRunAction statement in the Debug Viewer Command tab is not supported.

After you run a test with the local system monitoring option activated when the test is either very short, or the number of seconds entered for the Enable local system monitoring every: __ seconds option is high (a high percentage relative to the length of your entire test run), then when you select one of the last steps in the Run Results tree, the Current Step indicator in the System Monitor tab may jump to a position outside (to the right) of the graph.

Workaround: Add a Wait statement to the end of the test or reduce the number of seconds entered in the Enable local system monitoring every: __ seconds option.

When working with the .Object property in the Keyword View, it may take a long time for QuickTest to retrieve IntelliSense information for the step.

Workaround: Use the Expert View when working with the .Object property.


48

If a function library file referenced by a recovery scenario is missing, the Missing Resource pane does not indicate the missing file, but QuickTest alerts you about the problem when you select the Save Test with Resources option.

Workaround: The alert does not cause any problems with the save, so you can continue. After you save the files locally, save the missing function

library file locally and manually reset the association of the recovery scenario to the function library in your local copy.

When running in Maintenance Mode, if a step contains a programmatic description for an object that is not found in an application, it may take a while for Maintenance Mode to indicate there is a problem. If you use the option to point to the object, it may take a while for Maintenance Mode to reopen afterwards.

When the Maintenance Run Wizard cannot find an object, and the test object description for that object does not have any mandatory or assistive properties (it is identified only by its ordinal identifier, such as a Browser test object), then when you point to the object, the wizard is unable to fix the problem and displays a message that the object you pointed to has a test object description that is similar to the object that QuickTest could not identify.

Workaround: Use the Update from Application option in the Object Repository dialog box (for objects in the local respiratory) or in the Object Repository Manager (for objects in a shared object repository) to fix the test object description.

When your Windows Display settings are set to use large fonts, the text in the Maintenance Run Wizard screens may be truncated.

When the Maintenance Run Wizard cannot find an object in the application, and you point to a different object class to replace it, the Maintenance Run Wizard offers to add a step with that object and the objects default method. However, the wizard does not insert any method arguments for the step. If the step method has required arguments and you accept the step that the Maintenance Run Wizard proposes without modifying it, the step will fail when you run it.

Workaround: Enter valid method arguments for the step.


When you use the RunAction statement, you must specify the action name explicitly on the statement. You cannot use a variable. For example, you should write: RunAction="Action1[ExternalTest]" and not:aName="Action1[ExternalTest]"RunAction aName 49

If you make a copy of an existing test (either in the file system or in Quality Center), then you cannot insert a call to the same action from both of these tests into the same test.

Workaround: Instead of creating a copy of the test, use Save As to create a duplicate of the test.

You cannot run the Microsoft Script Debugger or the Microsoft Visual Studio debugger if QuickTest is configured to record and run test on any open Windows-based application (Automation > Record and Run Settings > Windows Applications).

Workaround: Do one of the following:

In the MicIPC section of the mercury.ini file (located in %SYSTEMROOT%) add these entries:devenv.exe=0msdev.exe=0msscrdbg.exe=0

Open the debugging program from a user account other than the one running QuickTest Professional.

If you try to open or associate a resource file other than a function library file (from the file system or Quality Center) and its extension is written in one or more upper-case letters, QuickTest displays a message that it cannot open files of this type.

Workaround: Change the file extension to lower-case letters and then try to associate the file again.

If you do not have at least one printer installed on your computer, you cannot use the Export Report option in the Test Results window.


50

You can use the RegisterUserFunc statement to register a user-defined function that will override an existing test object method. You can also register a user-defined function to override a test object method that was created using a QuickTest Professional Extensibility SDK. If you override this type of test object method, the user-defined function must not (recursively) call the test object method that it overrides. When selecting Record and run test on any open Web browser in the Web tab of the Record and Run Settings dialog box, the browser must be opened after you open QuickTest Professional. Otherwise, QuickTest will not record and run tests properly.

In the Step Generator, if you add an operation that returns an object, and the assignment in the test or component is missing a Set statement, the run session will fail.

When running a QuickTest test from a Quality Center test set or using QuickTest automation, the When error occurs during run session setting (File > Settings > Run node) is ignored. Instead, QuickTest automatically continues to the next step when an error occurs. If you want to change this setting, contact HP Software Support.

QuickTest does not record launching Windows Help from the Start menu.

When the title of a window changes during recording, QuickTest may fail to recognize objects within that window while running the test or component.

Workaround: Remove the text property from the windows test object description in the Object Repository dialog box.

Errors during the run session produce more than one error node in the results.

The GetItemProperty method may not correctly return the text property value for WinComboBox, WinList, WinListView, VbComboBox, VbList, and VbListView test objects.

Workaround: Use the GetItem method to retrieve the text property value for these test objects.

Running a test or component that contains a For Each statement that iterates on the ParameterDefinitions collection may fail if the collection was retrieved directly before using the For Each statement.

Workaround: Use other VBScript loop statements, such as For or While.


In versions of QuickTest earlier than 9.0, if you specified a path for a resource starting with \.., it was considered to be a relative path. In QuickTest 9.0 and later, a path that starts with \.. is considered to be a full path, with the backslash representing the root folder of the current drive.

If you defined paths starting with \.. using versions of QuickTest earlier than 9.0, you should change the path to be a standard relative path by 51

removing the backslash (\).

It is recommended not to use the VBScript On Error Resume Next statement, because it may interfere with the built-in error handling mechanism in QuickTest.

Workaround: Perform error handling in QuickTest using the Run pane of the Test Settings dialog box or use the OnError property of the RunSettings object through automation.

If a test containing an On Error Resume Next statement calls a function that does not contain a separate On Error Resume Next statement, no VBScript error handling will be applied if an error occurs within the function. In versions of QuickTest earlier than 9.0, On Error Resume Next statements worked correctly in this situation.

Workaround: Use QuickTest built-in error handling, or if needed, use On Error Resume Next within the function body.

The MouseMove method may behave unexpectedly in a VMware environment.

Workaround: Add the following line to the VMware configuration file (.vmx): vmmouse.present = "FALSE"

For more information, refer to the VMware support article, number 1691 - "Unexpected Cursor Behavior in Windows Virtual Machine with "Snap To" Mouse Control Panel Option Enabled", at: http://www.vmware.com/support/kb/enduser/std_alp.php.


52

When running QuickTest on a remote machine using a Remote Desktop Connection session (RDC) or using Citrix, if the remote session is minimized during the run session, or if the computer on which the application is being tested is logged off or locked, the following problems may occur:

the test or component run session may fail steps that contain keyboard or focus operations may fail

the Test Results still image capture and/or the Screen Recorder may display a black screen

steps for which the device level replay is configured to use the mouse (instead of browser events) to run mouse operations may fail. (You set the device level replay using a Setting.WebPackage("ReplayType") statement or by setting the Replay type option in the Advanced Web Options dialog box.)

Workaround: If you are using Citrix or a Remote Desktop Connection session to run a test or component, do not minimize the session window, and make sure that the computer on which the application is being tested is not logged off or locked.

You cannot create a call to a new action called Global, since Global is the name reserved for the Global sheet in the Data Table. If you create an action called Global, you will not be able to select the local or global data sheet when parameterizing a identification property.

If you define a VBScript class, it can be called only within the QuickTest action or function library in which you defined it.


ActiveX-related Issues

In the following ActiveX test object methods, if you specify the column by name, an error occurs when you run the test: ActivateCell, ActivateColumn, SelectCell, SetCellData, SelectColumn.

Workaround: When calling these methods, specify the column by number.53

When inserting steps in the Expert View for a Web application that has a mixed hierarchy of Java objects inside an ActiveX control, then it may take a long time for QuickTest to retrieve the possible argument values (dynamic list of values) for ActiveX arguments.

Workaround: Insert these steps using the Keyword View (where the dynamic list of values functionality is not used).

ActiveX controls inside Netscape Browser are not supported.

If QuickTest Professional does not recognize an ActiveX control inside a Web page, reduce the security level within your Microsoft Internet Explorer browser.

If an ActiveX controls internal properties have the same name as the ActiveX properties created by QuickTest Professional, retrieval and verification of such properties may be problematic.

Workaround: You can access the internal properties of an ActiveX control using the Object property.

Methods performed on row and column positions for Apex, DataBound, and Sheridan grids return the values of the visible positions and not the absolute positions within the tables.

Workaround: Use the scroll bar while recording in order to display the required cells.

When recording on an ActiveX control, wait for the recorded step to appear before moving the mouse. Moving the mouse too quickly may result in a corrupted Active Screen for that step.

The AcxTable.RowCount method is not supported for the Microsoft Data Bound Grid control.

QuickTest may fail to properly capture some of the internal properties of windowless ActiveX controls, such as x, y, height, and width.


54

Recording on windowless ActiveX controls may result in some additional steps added to your test or component (such as a Click method in addition to a Set method on an AcxRadioButton object). These additional steps will not cause the run session to fail.

Drag and Drop operations on windowless ActiveX controls are not supported. QuickTest may fail to recognize windowless ActiveX controls identified by programmatic descriptions.

Workaround: Add Windowless=True to the programmatic description.

Example:

set myButton = Description.CreatemyButton("progid").Value = "Forms.CommandButton.1"myButton("Windowless").Value = TrueDialog("ActiveX Collection Client").AcxButton(myButton).Click

Delphi- and Delphi Add-in Extensibility-related Issues

If you use the Object Identification dialog box to make changes to Delphi test objects that were created using Delphi Add-in Extensibility, these changes affect only the current QuickTest session. The changes are not retained when you close and reopen QuickTest.

Workaround: Make the changes in the Delphi Add-in Extensibility test object configuration file that defines the test objects. The Delphi Add-in Extensibility file is located in \dat\Extensibility\Delphi. (If working with Quality Center: \dat\Extensibility\Delphi.) If the Delphi Add-in Extensibility support set was developed by a third party, you might want to contact them to assist in making this change.


When you open the Delphi Add-in grid extensibility sample project, DelphiGridExtSample, in Delphi Studio, a "Class TStringDrawGrid not found" error message is displayed.

Workaround: Register the TStringDrawGrid custom control in Delphi Studio before opening the DelphiGridExtSample project. To do this, perform the following steps: 55

a In Delphi Studio, select Component > Install Component. The Install Component dialog box opens.

b In the Unit file name box, specify the full path for the StringDrawGrid.pas file. The file is located in: \samples\DelphiGridExtSample\Application.

c Click OK.

d If confirmation or information dialog boxes open, click Yes and/or OK, as necessary.

e The Package dialog box opens.

Note: If Delphi Studio displays the StringDrawGrid.pas file for editing at this point, instead of opening the Package dialog box, repeat steps a- d.

f Click Compile.

g Close the Package dialog box, and click Yes in the save confirmation box that opens.

h Open DelphiGridExtSample. The project opens without an error.

Java-related Issues

QuickTest does not record MouseDrag steps on JFC Java list controls.

Workaround: Enter the MouseDrag step manually.

QuickTest cannot record or run MouseDrag steps on SWT objects.

Workaround: Enter the MouseDrag step manually.


56

If you update object identification property settings for a Java object, the changes take effect only after restarting QuickTest.

.NET Web Forms-related Issues

QuickTest may recognize some Web Forms grids as WebTables instead

hp qtp 10.00 readme

Documents

quicktest professional

quicktest professional

hp support

hp passport login page

hp passport id

hp sales representative

whats new help

following information