QuickTest Professional 9.5 Readme
Software version: 9.5
Publish date: August 2008
This file provides the following information about the QuickTest Professional 9.5 version:
For detailed information about using QuickTest Professional, please see the documentation set, available from the QuickTest Professional Help menu.
Important:
Much of the information in this Readme file is incorporated in collapsed drop-down sections. To search these sections, expand them.
In addition to the information in this readme file, it is important to review the readme file of any hotfix or patch you install on QuickTest Professional. For more information, see Hotfix and Patch Information.
After you modify a test or other resource in QuickTest Professional 9.5, you cannot open it in a previous version. A hotfix will be made available to provide support for QuickTest Professional 9.2 tests and other resources.
Documentation
The first page of this readme document contains the following identifying information:
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 <QuickTest Professional\help> 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 What's New Help (Help > What's New) provides information about new features and supported environments in this version of QuickTest Professional.
- Detailed information about QuickTest Professional can be found in the HP QuickTest Professional User's Guide and HP QuickTest Professional Object Model Reference. These are available with a combined index and text search, along with the Microsoft VBScript Reference, from the Help menu (Help > QuickTest Professional Help). The HP QuickTest Professional User's Guide is also available in PDF format in the <QuickTest Professional installation>\help folder.
- The QuickTest Professional Automation Object Model Reference is available from the QuickTest Professional Start menu program folder and from the Help menu (Help > QuickTest Professional Help > QuickTest Advanced References > QuickTest Automation). It provides syntax, descriptive information, and examples for the automation objects, methods, and properties. It also contains a detailed overview to help you get started writing QuickTest automation scripts.
Hotfix and Patch Information
If you install a hotfix or patch over QuickTest Professional 9.5, 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.
Readme files for installed hotfix and patches are located in the <QuickTest installation>\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.
What's New in QuickTest Professional 9.5
QuickTest Professional 9.5 brings you an exciting array of new features to help you design and maintain your tests and components easier and faster. The new features include:
- All-in-one QuickTest Installation
- New QuickTest IDE Panes
- Process Guidance
- Maintenance Run Mode
- Checkpoint and Output Objects in the Object Repository
- Test Your PowerBuilder Applications in QuickTest
- Extend QuickTest Web Support for your Custom Web Objects
- Accelerate SAP Testing with Business Process Testing for SAP Applications
- Checkpoint and Output Value Steps Supported for Business Components
- Tolerance values for Bitmap Checkpoints
- Drag and Drop objects from Object Repository
- Replace Local Objects with Shared Objects After Export
- New Supported Operating Systems and Environments
For more information, see the What's New in QuickTest Professional Help (select Help > QuickTest Professional Help)
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.
To successfully install and run QuickTest Professional, your computer must meet the following minimum system requirements:
Note: Performance has not been optimized for the minimum system configuration. For best performance, your system should be configured using at least the recommended levels.
Add-in Specific System Requirements
In addition to the system requirements, some QuickTest Professional add-ins have additional requirements.
Supported Add-ins
You can install and use all QuickTest add-ins that are available in the QuickTest Professional 9.5 installation.
Supported Environments and Programs
QuickTest Professional is Unicode-compliant, and supports Unicode 2.0, UTF-8, and UTF-16.
HP Applications »
QuickTest Professional supports working with the following HP applications:
QuickTest Professional supports creating, recording, and running tests or components using the environments and programs described below. Click a link to view the supported programs and versions for each category.Virtualization Technologies »
Microsoft Office »
Microsoft Excel
When using Microsoft Excel files with QuickTest Professional (for example, to import or export data from or to the Data Table), you can work with Microsoft Excel 2002, 2003, XP, and 2007.
Microsoft Query
When using Microsoft Query with QuickTest Professional (for example, for Database checkpoints), you can work with Microsoft Query 2002, 2003, XP, and 2007.
ActiveX »
QuickTest Professional provides support for creating and running tests on the following when the ActiveX Add-in is loaded:
Grid Controls
In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Grid controls:
Calendar Controls
In addition to built-in support for ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Calendar controls:
Java Applications »
The QuickTest Professional Java Add-in supports creating and running tests on the following when the Java Add-in is loaded:
.NET Applications »
The QuickTest Professional .NET Add-in supports creating and running tests on the following when the .NET Add-in is loaded:
.NET Framework
The QuickTest Professional .NET Add-in supports .NET Framework 1.1, 2.0, 3.0, and 3.5.
WPF Controls
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.
Following is a list of the control types supported for WPF applications.
.NET Windows Forms
The QuickTest Professional .NET Add-in supports:
Following is a list of the control types supported for .NET Windows Forms applications.
In addition to the controls listed above, 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
Tips: To view the full type name of an object in your application, view the SwfTypeName test object 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..NET Web Forms
The QuickTest Professional .NET Add-in supports creating and running tests using most of the common .NET Web Forms controls.
Following is a list of the control types supported for .NET Web Forms applications.
Oracle Applications »
The QuickTest Professional Oracle Add-in supports creating and running tests on the following when the Oracle Add-in is loaded and the following is installed:
Toolkits
Environments
PeopleSoft Applications »
The QuickTest Professional PeopleSoft Add-in supports creating and running tests on PeopleSoft applications 8.X (8.0, 8.4, 8.8, 8.9, 9.0) with PeopleTools 8.4X (8.40, 8.41, 8.42, 8.43, 8.44, 8.45, 8.46) when the PeopleSoft Add-in is loaded.
PowerBuilder Applications »
The QuickTest Professional PowerBuilder Add-in supports creating and running tests on PowerBuilder applications 9.5, 10, 10.5, and 11 when the PowerBuilder Add-in is loaded.
SAP Applications »
The QuickTest Professional Add-in for SAP solutions supports creating and running tests when the Add-in for SAP solutions is loaded.
SAP Gui for Windows
The QuickTest Professional Add-in for SAP solutions supports testing of SAP Windows objects created using at least:
Refer to the HP QuickTest Professional Add-ins Guide for more information on required server versions and other required configurations.
Note: eCATT is not supported with QTP 9.5. A hotfix will be made available to provide support for eCATT.
Web-based SAP
The QuickTest Professional Add-in for SAP solutions supports testing on the following SAP Web-based application versions:
- SAP Gui for HTML (ITS) 6.10
- SAP Gui for HTML (ITS) 6.20 (patch levels 12 or 13)
- SAP Enterprise Portal 6.0
- SAP Enterprise Portal 7.0
- SAP Interactive Center WebClient 1.0
Note: The patch levels mentioned in the supported environments above are the minimum supported levels for the QuickTest Professional Add-in for SAP solutions. 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.
Integrating the Add-in for SAP solutions with Other Testing Environments
Siebel Applications »
The QuickTest Professional Siebel Add-in supports recording and running tests and components on the following versions of Siebel eBusiness applications:
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.
Stingray Applications »
QuickTest supports the following environments with the QuickTest Professional Stingray Add-in:
- Stingray Objective Grid / Objective Toolkit version combinations (in either Unicode or non-Unicode—QuickTest does not support both Unicode and non-Unicode in the same application)
- Amdocs ClarifyCRM (contains Stingray Grid objects), versions 10.0—12.1
Terminal Emulator Applications »
The QuickTest Professional Terminal Emulator Add-in has built-in support for testing on the following terminal emulator applications:
If you are using a newer version of one of the emulators listed above, or your emulator version is different from one listed above 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 Age Smalltalk Applications »
The QuickTest Professional VisualAge Smalltalk Add-in supports testing the following VisualAge Smalltalk 6.0.2 widget classes.
Note: The QuickTest Professional VisualAge Smalltalk Add-in has been tested on and formally supports VisualAge Smalltalk, version 6.0.2. However, you may also be able to use the QuickTest Professional VisualAge Smalltalk Add-in with VisualAge Smalltalk versions 4.2 and later.
Visual Basic Applications »
QuickTest Professional supports testing on Visual Basic 6.0 applications.
Note: Visual Basic .NET applications are supported by the QuickTest Professional .NET Add-in.
Web Browsers »
You can create and run tests and components using the following browser versions:
Web Services »
The QuickTest Professional Web Services Add-in supports the toolkits, environments, and programs listed below.
Toolkits
Other Environments and Applications
Useful Information
General—Useful Information »
- You must be logged on with administrator privileges to install QuickTest Professional.
- If you are upgrading to QuickTest Professional 9.5, you need to first uninstall your previous version of QuickTest Professional and the Quality Center Add-in (if installed).
- You can use the Save and Restore Settings utility to save your existing customization settings, registry keys, and tests before you uninstall an old QuickTest version, and then restore them after you install a new version.
This means that you will not need to reconfigure your preferences. The Save and Restore Settings utility is particularly useful for saving the manual customizations made to extensibility .xml files.
For more information, open the Save and Restore Settings utility as described below and click the Help button.
To save existing settings and tests:
- Before uninstalling your previous QuickTest version, run the SaveRestoreSettings.exe file located in the root of the QuickTest installation DVD. The Save and Restore Settings dialog box opens.
- Select the Save settings to radio button option and enter the location and zip file name in which you want to save your existing QuickTest Professional customization settings, registry keys, and tests.
- Click OK to save your settings and tests.
To uninstall a previous version of QuickTest:
Use the Add/Remove Programs option in the Windows Control Panel (available from the Start menu).
To restore saved settings and tests:
- After installing QuickTest Professional 9.5, choose Start > Programs > QuickTest Professional > Tools > Save and Restore Settings. The Save and Restore Settings dialog box opens.
- Select the Restore settings from radio button option and enter the location and zip file name in which your QuickTest Professional customization settings, registry keys, and tests are saved.
- Click OK to restore your settings and tests.
- To use QuickTest Professional's 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 Microsoft's 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 9.5, you must install version 9.0 or later of the HP (Mercury) Functional Testing Concurrent License Server (available from the QuickTest Professional installation DVD). QuickTest Professional 9.5 is not compatible with earlier versions of the HP Functional Testing Concurrent License Server.
- If certain object property values in your application are generated dynamically for all objects of a given type, you can create a property pattern configuration file that instructs QuickTest Professional to automatically record the object property as a regular expression. For detailed instructions about how to use the Property Pattern feature, see PropPattern.htm located in the <QuickTest Professional installation>\help folder.
Java—Useful Information »
.NET—Useful Information »
- Do not load the .NET Add-in if you are using the Oracle Add-in to test Oracle applications.
- 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 above 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 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:
- Log-in to your computer with administrator permissions.
- Open a Command Prompt (Start > Programs > Accessories > Command Prompt).
- Type cd /d <QuickTest Professional installation path>\bin and press Enter to change the path to the QuickTest Professional bin folder.
- 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
Oracle—Useful Information »
- The QuickTest Professional Oracle Add-in supports working with Java clients (not Windows clients).
- 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 about using the Name attribute in test object descriptions, refer to the HP QuickTest Professional Add-ins Guide.
PeopleSoft—Useful Information »
SAP—Useful Information »
- A function library that extends the testing capabilities on SAP Gui for Windows applications is available in <QuickTest installation folder>\dat\BPT Resources. The function library file name is SAP.txt. To use this function library with business process testing, upload the file as an attachment to your Quality Center project. For more information on the SAP.txt function library, refer to the HP QuickTest Professional Add-ins Guide. For more information on business process testing, refer to the HP Business Process Testing User's Guide.
- In the Windows Applications tab of the Record and Run Settings dialog box, choose 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.
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.
- 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, refer to 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.
Testing SAP Web-based Applications
Siebel—Useful Information »
Information for All Supported Siebel Versions
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 in order to use the Siebel Add-in. If you install QuickTest Professional and then install the Siebel Add-in immediately afterward, all other add-in selections are automatically cleared in the Add-in Manager dialog box when you open QuickTest Professional for the first time.
- It is strongly recommended that when testing Web applications that do not contain Siebel objects, you do not load the Siebel Add-in.
- The Web event configuration settings and the object identification definitions for Web and Siebel objects are set automatically when the Siebel Add-in is loaded. You cannot access the object identification definitions for Web or Siebel objects.
- 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.
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, refer to 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, refer to 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 loaded—RepositoryName, UIName, and SiebelObjType. The property values may be empty for some of the objects.
Stingray—Useful Information »
The following special properties are available for checking Stingray controls:
Terminal Emulators—Useful 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, refer to the Utility 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, choose 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 tab.
Notes and Limitations
This section includes information and limitations about QuickTest Professional 9.5.
This section includes notes and limitations on the following topics (each sub-divided according to add-in):
General Issues
Java—General Issues »
- 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").Activate
This extra step generally does not affect the run session adversely.Workaround: Before running your test or component, remove the extra step that was recorded.
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, refer to the HP QuickTest Professional Add-ins Guide.
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)
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
Workaround: Use other verification methods (such as using GetTOProperty). For more details on verification methods, refer to the HP QuickTest Professional User's 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 name naming the test object when running in JDK 1.6 is different than the one used when running in JDK 1.5.
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, then when you run it on JDK 1.6, the test or component may fail.
Workaround:
- For a JavaButton object—relearn 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.
- For a button in a JavaToolbar—modify the Item argument in the JavaToolbar statement to refer to the relevant button. You can specify the button's 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.
- 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 the HP QuickTest Professional Java Add-in Extensibility SDK. If you override this type of test object method, the user-defined function must not call the test object method that it overrides.
Oracle—General Issues »
Workaround: Use the numeric index instead of the string as the argument value.
Workaround: Add an OracleTabbedRegion.Select method to the appropriate tab before any replay step on an object inside a tab which 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 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.
PeopleSoft—General 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.
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.
- 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.
WPF—General 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 are not set up 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.
- IntelliSense is not supported for the AutomationPattern test object property.
.NET Windows Forms—General Issues »
- When you spy on a .NET Windows Forms object (using either the Object Spy or the .NET Windows Forms Spy), and the Record and Run settings are not set up to record on the .NET Windows Forms application on which you are spying, QuickTest recognizes the object as a Standard Windows object.
Workaround: Close your .NET Windows Forms 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 .NET Windows Forms application and then spy on it again.
- 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, choose the Tools > Options > Active Screen tab 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.
- 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 form 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 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.
- When working with Infragistics UltraWinGrid, recording and/or run of the SwfTable.Sort operation may work incorrectly if the table is grouped by a particular column.
- If you enter data in a .NET Grid control, the SwfTable.SetCellData operation is recorded only when you leave the cell (select another cell).
- Operation on a grid cell that was selected before you start 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 operation on a cell which is already selected move focus to another cell, then select the required cell while recording and perform the required operation.
.NET Web Forms—General Issues »
- .NET Web Forms support does not work correctly when the SAP or Siebel add-ins are loaded.
Workaround: Make sure that check boxes for the SAP and Siebel add-ins are cleared in the Add-in Manager dialog prior to using the .Net Add-in with Web Forms.
- 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. Refer to the .NET Web Forms Object Model Reference Help for details.
- 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 test object properties is always none for WbfCalendar objects in selection mode none.
- To retrieve correct values for WbfCalendar Selected Date and Selected Range test object 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.
- WbfUltraGrid may fail to sort columns in a descending order when the column is not already sorted.
Workaround: Split the Sort call into two calls—first 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"Stingray—General Issues »
Installation and Configuration
QuickTest Professional—Installation Issues »
- The information and URL link provided on the License Installation Welcome Screen, for both QuickTest Professional and the Functional Testing Concurrent License Server, are no longer valid.
Workaround: For information on how to submit your locking code and request a license key, refer to the licensing information provided in your package, or contact your HP Functional Testing Products supplier or HP Software Support.
- The path in which installation files for QuickTest Professional are located, and the path in which QuickTest Professional are installed, can contain only English characters.
- If you install QuickTest 9.5 on a computer that previously had an older, licensed version of QuickTest, QuickTest may not detect the previous license after installation. In all cases, the limited day demo license dialog box opens.
- 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 a HP Functional Testing Concurrent License Server and license key installed.
- 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, we recommend installing a newer version from: http://support.microsoft.com/kb/q293623/. This will be recognized during installation and QuickTest Professional will instruct you to download the corrected DLL from the Microsoft site.
- If you install QuickTest Professional on a computer that also has Microsoft HTML Help Workshop installed, you may receive the following error message when you try to compile a help project in Microsoft HTML Help Workshop: The file itircl.dll has not been registered correctly.
Workaround: Look for itcc.dll on your system (in \windows\system or \winnt\system32). If you find it, register it using regsvr32.exe. If the itcc.dll is not on your system at all, you can download a copy from: http://www.mvps.org/htmlhelpcenter/htmlhelp/hhtips.html#hhc6003. You may have to restart your computer before using HTML Help Workshop again.
- Installing QuickTest Professional on a network drive is not supported.
- When working with a terminal server (for example, Windows 2000 Server or 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 (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-in—Installation 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.
- In Windows XP and Windows 2003, after you install the QuickTest Professional Java Add-in 9.5, 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-in—Installation 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, refer to 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 8.2, 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.
Stingray Add-in—Setting Up Support for Stingray Objects »
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. You can open the Stingray Support Configuration Wizard as the last step when running the setup application for the Stingray Add-in. 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 for different Stingray application versions, launch the wizard by selecting it from the QuickTest program group, or, in QuickTest, from the Stingray tab 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 running—with or without the add-in loaded—unexpected 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 <QuickTest installation folder>\bin\StingrayAgent\AgentDll\MFC<##>\OG<####_OT<####> and in <WinRunner installation folder>\arch. Then replace the earlier file with the later one.Terminal Emulator Add-in—Installation and Configuration 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.
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 emulator's configuration settings. For more information, refer to 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.
Creating, Editing, and Running Testing Documents
General Issues »
- During a maintenance run (Automation > Maintenance Run Mode), if the wizard cannot find an object because the parent object changed, and you point to the missing object's parent object (instead of the missing object itself), the wizard will add a step containing the parent object and its default method. For example, suppose a button object is missing. If you point to its parent object in the wizard (such as a window), QuickTest will insert the following step:
Window("Cal_2").Active
Instead of:
Window("Cal_2").Button("Button").Click
Workaround: Run the maintenance run mode again and choose the relevant child object.
- If you spy on an object in Visual Basic or ActiveX applications using the Object Spy, and the Record and Run settings are not set up to work with the application on which you are spying, QuickTest recognizes the object as a Standard Windows object.
Workaround: Close your application. In QuickTest, open the Record and Run Settings dialog box (Automation > Record and Run Settings) and, in the Windows Application tab, do one of the following:
- Select the Record and run test on any Windows application option, or
- Specify your application's details in the Application Details area. (Make sure that the Applications specified below check box is selected).
Reopen your application, and then spy on it again. (Note that this limitation is also relevant for spying on Windows Presentation Foundation (WPF) objects using the Object Spy or using the .NET Windows Form Spy when the .NET Add-in is loaded.
- When choosing 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.
- QuickTest Professional uses Microsoft Regular Expressions, in which the character . represents any character except \n. In older versions of QuickTest Professional, this character represented any character.
Workaround: Change the . character to [.\n].
- In the Step Generator, if you add a method that returns an object and the assignment in the test or component is missing a Set statement, the run session will fail.
- The behavior of the Timeout argument of the Exist method was changed between QuickTest version 6.5 and version 8.x. In version 8.x and later, it behaves as follows:
- If a timeout value is specified, QuickTest waits until it finds the object or until the timeout is reached.
- If the value 0 is specified, the method returns the True or False value immediately.
- For tests, if no value is specified, the value specified in the Test Settings dialog box for the Object Synchronization Timeout is used. For components, the default setting of 20 seconds is used.
To return to the 6.5 default behavior (default timeout is zero):
- Add a 0 value for the timeout argument for all Exist statements.
- Use the RegisterUserFunc statement in a library file to modify the behavior of Exist to equal Exist(0) and then associate the library file with all relevant tests.
Note: It is not recommended to set the Object Synchronization Timeout to 0, as this will prevent QuickTest from recognizing objects that take time to load. Additionally, there are other methods that use the Object Synchronization Timeout as the default value, such as WaitProperty and Sync.
- 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 tab) 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 for more information.
- 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 window's 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.
- Prior to QuickTest 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 earlier versions of QuickTest, you should change the path to be a standard relative path by 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 tab 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 earlier versions of QuickTest, 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 (<VM name>.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.
- 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 test object property.
- When you choose to delete a call to an action from the Test Flow pane, the confirmation message that opens (incorrectly) implies that the action will be deleted from the test and not just this call. However, clicking OK in this message deletes only the selected action call. You can still insert the action back into the test from which it was removed, or into any other test, using the Insert Call to Existing Action option (correct behavior).
- Integration with SAP eCATT is not supported. To obtain a patch that provides SAP eCATT support, contact HP Software Support.
- 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 »
- ActiveX objects 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 control's internal properties have the same name as ActiveX properties created by QuickTest Professional, retrieval and verification of such properties may be problematic.
Workaround: You can access the internal properties of 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.
- 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.Create
myButton("progid").Value = "Forms.CommandButton.1"
myButton("Windowless").Value = True
Dialog("ActiveX Collection Client").AcxButton(myButton).Click
Java-related Issues »
.NET-related Issues »
Oracle Applications-related Issues »
PowerBuilder-related Issues »
- When you work with PowerBuilder DataWindow objects while the Active Screen Capture option is enabled (any value other than None), recording of cell operations may be slow if the DataWindow control contains many elements.
Workaround: Set the Active Screen capture level to None.
Note: If you set the capture level to None, you cannot add checkpoint or output value steps for the DataWindow's inner-properties from the Active Screen, Keyword View, or Expert View while editing the test, or from the Keyword View while editing the component.
- If a step sets value to a cell and then the immediate next step is a PBDataWindow.GetCellData step on the same cell, the GetCellData step returns the old value, instead of the value that was set in the previous step.
Workaround: The DataWindow control refreshes a cell's value only when the focus changes. Therefore, to solve the problem, insert a step prior to the GetCellData step that changes the focus to another cell (such as a SelectCell step).
SAP—Testing Windows-based SAP Application »
- Consider the following guidelines when working with toolbar controls:
- Separate toolbar controls (ones that are not part of a grid or other object) are supported by the SapGuiToolbar test object (GuiComponentType is 202) and the Object Spy recognizes them because they are separate objects.
Note that tree controls do not have associated toolbars. Toolbars displayed on top of tree controls are recognized as separate toolbars, and therefore are supported as described above.
- Toolbars inside grid controls are supported by the SapGuiToolbar test object (GuiComponentType is 204). However, the Object Spy does not recognize these toolbars because they are part of the grid. You also cannot add these toolbars to the object repository using the Add to repository option from the Active Screen or the Add Objects option in the Object Repository dialog box. You can add these toolbars to the object repository only by recording on them.
- Toolbars inside other controls (such as a toolbar within a text area control) are not supported.
- Microsoft Office controls within the SAP window are not supported.
- If you record the step of pressing an F4 key, and that key press results in setting new values for multiple fields, a step is recorded only for the field from which the F4 key was pressed, and therefore, only that field will be populated during the run.
- Right-click operations are not supported for the SAPGuiTextArea object.
- The SAP Editor control is not supported.
- The SAP Gantt chart (SAP Bar Chart) and Image/Picture controls are supported by the SAP Gui for Windows alternative recording mechanism. 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.
- Some methods that were available for the APO grid in earlier versions of the SAP API are no longer supported. Therefore, these methods have also been removed from the SAPGuiAPOGrid test object.
- Drag-and-drop operations in the SAP Gui for Windows application are disabled when QuickTest is open.
- Running a test on HTML elements embedded in an SAP Gui for Windows application may result in an "Object is disabled" error. This may happen if the HTML control is not ready for the test run.
Workaround: Add a Sync statement such as SAPGuiSession.Sync or a Wait statement to the script in order to run the test successfully.
- By default, the recording and running of steps on HTML elements embedded in an SAP Gui for Windows application is performed using the QuickTest Professional Web Add-in. In some cases, steps recorded using the Web Add-in are inserted into the script before SAP Add-in steps that use the SAP Scripting API.
Workaround: Use the option of recording HTML elements embedded in SAP Gui application using the SAP Scripting Interface. To do so, stop recording, select the Record HTML elements using SAPGui Scripting interface check box in the SAP tab of the Options dialog box (Tool > Options > SAP tab). Then close and reopen the test and then begin recording again. For more information, refer to the HP QuickTest Professional Add-ins Guide.
- When you insert a copy of an action or when you insert a call to an action, but select Use a local, editable copy in the Parameter data section of the Insert Call to Action dialog box, QuickTest copies the action's data sheet to the test. However, if the called or copied action includes an SAPGuiTable.Input, SAPGuiGrid.Input, or SAPGuiAPOGrid.Input statement, the corresponding input data sheet is not copied to the Data Table with the action.
Workaround: Insert and run Datatable.AddSheet and Datatable.ImportSheet statements to import the sheet referenced by the action's Input method. Ensure that the name of the data sheet exactly matches the name specified in the corresponding Input statement.
- When using the SAPGuiTable Input method, check the scrolling mode of the current table. If you parameterize a table with a Data Table sheet that contains more rows in the sheet than are displayed in the table's current view, QuickTest tries to scroll down the table while running the test, to insert more rows from the data sheet. QuickTest supports two ways of scrolling rows in tables—by pressing the Enter key, or by pressing the PageDown key. By default, the Add-in for SAP solutions tries PageDown if needed. You can configure the required mode using the second argument of the Input method.
For more information, refer to the HP QuickTest Professional Add-ins Guide.
- In the SAP Enterprise Portal environment, occasional synchronization problems may occur during the test run when alternating between SAP Web and SAP Windows environments.
Workaround: Add a WaitProperty or Wait statement between the Web steps and the Windows steps.
- QuickTest fails to run steps on SAP tree nodes that contain the ";" character.
- The QuickTest Professional Add-in for SAP solutions connects to your SAP Logon or SAP Logon Pad application for recording and running tests on SAP Gui for Windows sessions. If you use both SAP Logon and SAP Logon Pad processes on your desktop, QuickTest Professional will connect to the latest process that was launched.
- Use the SAP tab of the Record and Run Settings dialog box to instruct QuickTest to open your SAP Gui for Windows application. Do not use the Windows Applications tab of the dialog box for this purpose.
For more information, refer to the HP QuickTest Professional Add-ins Guide.
- For security reasons, the SAP scripting API prevents the recording of passwords. When you record the operation of inserting a password in a password box, QuickTest records a Set statement using asterisks (****) as the method argument value.
Workaround: Record the password normally during the recording session. After the recording session, modify the password step to use the SetSecure method, and enter the encrypted password value or parameterize the value.
For more information, refer to the SAP Windows section of the HP QuickTest Professional Object Model Reference (Help > QuickTest Professional Help > Object Model Reference > SAP Windows).
- QuickTest does not record HTML objects in SAP Gui for Windows applications.
- The QuickTest Professional Add-in for SAP solutions does not automatically record standard Windows dialog boxes used by your SAP Gui for Windows application (such as the Open File and Save As dialog boxes). The SAP scripting API does not support these dialog boxes. This may also occur when using SAP Gui for Windows with GuiXT.
Workaround: Change to Standard Windows Recording mode (choose Test > Standard Windows Recording or click the Standard Windows Recording toolbar button) to record on these objects. Alternatively, use low-level recording to record on these objects or use programmatic descriptions to run steps on these objects.
Note: If you switch to Standard Windows Recording mode after performing an operation on a standard Windows control, in some cases this may cause both QuickTest and the SAP application to become unresponsive. To avoid this, make sure that you switch to Standard Windows Recording mode before you perform the operation that opens the standard Windows control in your SAP application.
SAP—Testing Web-based SAP Applications »
SAP Enterprise Portal
- Operations on the iView option menu and on objects within the page title bar of SAP Enterprise Portal are recorded as Web operations on the Frame object and not as SAP operations on the iView object.
- Minimized or collapsed iViews may not be recognized correctly.
- In some cases when more than one browser is open during the test run, QuickTest is unable to correctly identify certain objects.
Workaround: Clear the Enable Smart Identification check box for the Browser test objects in the Object Repository dialog box. You may also want to disable the Enable Smart Identification option for Browser test objects in the Object Identification dialog box for future test recording.
- In some cases, a frame in SAP Enterprise Portal may be recognized as a Web Frame object instead of an iView object. In some of these, the frame name is generated dynamically. Because the Web Frame object uses the name property to identify the object, you must modify the recorded name value to use an appropriate regular expression so that QuickTest will be able to recognize it during the test run.
SAP Gui for HTML—Internet Transaction Server (ITS)
- When testing your SAP Gui for HTML application on Windows XP, it is recommended to use the Windows Classic theme instead of the Windows XP theme, to improve performance.
- When using the Object Spy or creating a checkpoint on an object inside an SAP Web table cell, QuickTest may recognize the object as a WebElement (and not as the appropriate SAP Web object), if a click has not yet been performed on the object.
Workaround: Click on the object inside the SAP Web table cell before using the Object Spy or creating a checkpoint on it.
- Dragging the SAP Gui for HTML table scroll bar is not recorded.
Workaround: You can record scrolling in SAP Gui for HTML tables by clicking the scroll button. Alternatively, use the Step Generator or Expert View to insert a SAPTable.Object.DoScroll("up") or SAPTable.Object.DoScroll("down") statement in your test.
- The appearance of toolbar buttons may differ, and toolbar buttons may or may not be displayed, depending on the size of your browser window.
Workaround: Try to maintain the same browser window size and the resulting menu appearance when recording and running your test.
- When running a test on an ITS frame in an SAP Enterprise Portal iView, the ITS menu sometimes fails to operate properly.
Workaround: Enlarge the iView size and/or increase the Object Synchronization Timeout and then run the test again.
Siebel 7.7.x and Later—Creating and Running Tests and Components »
- Certain objects, for example, in the SmartScript module, do not have a value for the repository name property and are therefore not recorded and are not recognized by the Object Spy.
Workaround: Use low-level recording.
- Gantt chart operations and RichText editor toolbar operations are not recorded.
Workaround: Use low-level recording.
- The appointment calendar object can be recorded only if the ActiveX Add-in is enabled.
- If you record the creation of a new appointment in an appointment calendar, the test or component may fail when you run it.
Workaround: Manually add an onkeypress FireEvent to the WebElement before the Set step.
- The Active Screen is empty for steps recorded on pop-up tables.
- Inner objects that are placed in cells of a SiebList object cannot be accessed in the standard way, even if they are recorded. This may cause the following limitations:
- The entire SiebList object is highlighted if the test or component script line contains an operation on a SiebList inner object.
- The ChildObjects method for SiebList objects returns 0.
- The Add Objects option in the Object Repository dialog box cannot be used to add SiebList inner objects to the object repository.
- If a warning message opens while recording your test or component, for example, if you insert invalid data, QuickTest may record these operations in the incorrect order.
Workaround: Manually change the order of the steps in your test after recording.
- Context-sensitive help (F1 Help) may not be available for Siebel 7.7.x, 7.8.x, and 8.0.x objects and/or methods that were added by Siebel after the Siebel 7.7 GA release. In addition, auto-documentation (in the Keyword View Documentation column) and step documentation (in the Step Generator) may not be available for these objects and/or methods.
Siebel 7.0.x and 7.5.x—Creating and Running Tests and Components »
- QuickTest does not support recording on Siebel applications using keyboard shortcuts.
Workaround: Use the mouse to record on Siebel applications.
- When you click the Search icon for the first time during a browser session, a frame opens that is different from all other search frames. When running test iterations, the correct frame may not be identified.
Workaround: Close the browser at the end of every iteration.
- QuickTest does not record the scrolling of a set of records in an SblTable.
Workaround: While recording, scroll the table row by row.
Tip: You can use the Expert View to manually edit the statement to scroll multiple rows.
- By default, QuickTest does not record Editor control operations (used mainly in long Description fields).
Workaround: Use low-level recording, making sure you record the scrolling to the control if needed.
- Each Siebel version includes changes/modifications to the user interface. As a result, steps created on previous Siebel versions on elements that no longer exist in the interface will probably fail and should be replaced.
For example, the button arrow used to view the next set of records on the top line of the Siebel table that appears in previous versions of Siebel was replaced in Siebel version 7.5.2 with a scrollbar at the side of the table. In this case, replace Image("Next Record").Click with an operation on the scrollbar.
- The name of the first column in an SblTable object cannot be retrieved.
Workaround: Use the column index to perform the operation on the cells in the first column.
Standard-Interactivity (SI) Applications
- In some SI application dialog boxes, in cases when selecting a check box causes a navigation to occur (for example, in a check box table column, such as the New column), QuickTest may not record the subsequent steps or may record them inaccurately.
Workaround: To continue recording accurately, click anywhere in the page before the next operation.
- When recording on a Currency Calculator pop-up control, clicking OK immediately after entering a currency value may result in a recording error.
Workaround: Before clicking OK in a Currency Calculator pop-up control within an SblAdvancedEdit object, select another control within the pop-up and then click OK.
High-Interactivity (HI) Applications
- Depending on your browser's security settings and the Siebel patches that are installed, several dialog boxes may open when logging in to your Siebel application. It is recommended to run tests or components when all required Siebel patches are downloaded and installed. If for some reason, you cannot do this, manually delete the Sync steps added between the steps recorded on the security alerts.
- QuickTest cannot record an SblTable.Sort operation if it is the first operation inside an MVG (Multi-Value Group) applet.
Workaround: Click anywhere in the MVG applet and then sort it.
- An SblAdvancedEdit object can open a pop-up object. QuickTest records only the Set method and does not record the operations within the pop-up object. However, if you open a table from the pop-up object, QuickTest does record the operations performed within this secondary table. These statements are not required in the test or component, since the operation of inserting the Pickup table selected item into the main table is also recorded. In some cases, these redundant statements interfere with the run session.
Workaround: If the test or component does not run as expected, delete the statements recorded on secondary tables opened from a pop-up object.
- When adding an attachment to a Siebel table, QuickTest records additional statements that may interfere with the run session.
Workaround: After recording, delete the OpenCellElement and Add statements that were recorded when you added an attachment.
- When inserting a value into a Siebel table cell using the Currency Calculator control, QuickTest may record a new SelectCell step before the SetCellData if you move the cursor to another cell before clicking in the cell in which you entered a value.
Workaround: While recording, always close the Currency Calculator by pressing the Enter key. If, for some reason, the Currency Calculator was not closed using the Enter key, you can manually change the order between the SetCellData and SelectCell steps.
Standard Windows Objects—Creating and Running Tests and Components »
- You cannot insert a checkpoint on a WinMenu object.
Workaround: Use the CheckProperty and CheckItemProperty methods to check specific property and item property values.
- If you record using Windows logo key shortcuts, the recording may be inaccurate.
Workaround: Use the Start menu instead of the Windows logo key when recording.
- Changing the style of a WinCalendar (from single selection to multi-selection, for example) will cause the run session to fail.
- When using the pointing hand mechanism from the Object Spy to point on MFC static text or tab controls, QuickTest may fail to return the correct object.
Workaround: Add the object to the object repository. To do this, point to the object's parent window, select the parent window object in the Object Selection dialog box, click OK, and perform one of the following in the Define Object Filter dialog box:
- Select the All object types option to add all of the objects in the parent window to the object repository.
- Select the Selected object types option, click the Select button, and then choose the specific object type(s) you want to add to the object repository.
After you add the object to the object repository, you can use the GetROProperty method to retrieve its run-time properties. For example:
width = Dialog("Login").Static("Agent Name:").GetROProperty("width")
MsgBox width- If you try to learn all objects in the top-level window of an application that has non-modal dialog boxes open, only the top-level window child objects and dialog box objects are learned. Child objects in the dialog boxes are not learned.
Workaround: To learn all child objects of all non-modal dialog boxes in a window, choose Tools > Options > Windows Applications > Advanced button, and select the Always enumerate child windows option.
Note that this option significantly affects the performance of recording and running steps.
Stingray Applications—Creating and Running Tests and Components »
The Stingray Add-in enables you to record and run tests and components on Stingray controls.
Objective Grid—QuickTest records and runs operations on grids using WinTable methods.
Objective Toolkit—QuickTest records and runs operations on tree controls using the WinTreeView methods, tab controls using the WinTab methods, and toolbar and menu bar controls using the WinToolbar methods.
For more information, refer to the Stingray section in the HP QuickTest Professional Object Model Reference (Help > QuickTest Professional Help > Object Model Reference).
Tip: A grid cell may display raw data or formatted data. The GetCellData method retrieves the raw data in the cell. To get the displayed (formatted) data, use the GetCellDisplayedData method.
Other Known Problems and Limitations
- By default, only single-threaded Stingray applications are supported.
To provide support for multithreaded applications, in QuickTest, choose Tools > Options > Stingray tab. Select the Support multithreaded Stingray applications check box and click OK. Close and restart QuickTest.
For more information, refer to the HP QuickTest Professional Add-ins Guide.
- This add-in does not support Objective Edit or Objective Chart controls.
- The ExpandAll method is not supported for Stingray tree controls.
- Sometimes, the MFC internal map that correlates a window handle of a control with a Visual C ++ object may not contain an entry for all Stingray controls. In such a situation, the Stingray Add-in may fail to recognize certain Stingray controls because it relies on this map when retrieving information from the application.
Workaround: The Stingray Add-in contains an auxiliary mechanism that serves as a fallback for the lack of MFC map entries in the situation described above. To activate this mechanism, in QuickTest, choose Tools > Options > Stingray tab. Select the Cache MFC map check box and click OK. Close and restart QuickTest.
Note: This mechanism is not activated by default because it imposes some performance overhead.
- When working with nested tab controls, you may need to manually modify the corresponding entries in the object repository to enable unique identification. For example, you may need to add an ordinal identifier to the existing description.
- By default, edit boxes, check boxes, and drop-down (combo) lists are supported when recording on a Stingray grid. Other types of controls embedded in Stingray grids may be supported partially or may not be supported at all.
Note: The CGXTabbedComboBox control and the CGXCheckBoxEx control type are not supported during recording.
Workaround: To work with controls other than the supported ones, manually add SetCellData statements to your test or component (instead of recording user actions inside cells).
- GetCellData and SetCellData methods are limited to 3000 characters.
- By default, only the following grid classes are supported:
To work with other grid classes that are derived directly from CGXCore, contact HP Software Support.
Terminal Emulators—Recording and Running Tests and Components »
- When working with the IBM PCOM emulator, QuickTest may ignore special European language characters while recording or running a test or component.
Workaround: Set the code page for your IBM PCOM emulator in QuickTest, using the Tools > Options > Terminal Emulator > Adjust Configuration > Emulator settings > Code page number (IBM PCOM only) option.
Tip: Try setting the Code page number (IBM PCOM only) option to 1252.
- The QuickTest Professional Terminal Emulator Add-in can identify emulator window objects only when the emulator is connected. For example, you cannot use the following statement to connect to an emulator session:
TeWindow("TeWindow").WinMenu("Menu").Select "Communication;Connect"
Workaround: You can record any steps that need to be performed prior to connection with the emulator. These steps are recorded as if the Terminal Emulator Add-in is not loaded. Once the emulator is connected, stop the recording session and begin a new recording session to record terminal emulator objects.
- When using an emulator that supports HLLAPI, if your emulator session disconnects from the host while recording, QuickTest no longer recognizes the emulator, even after reconnecting.
Workaround: Stop recording, reconnect the session, and continue recording.
- When recording on a Hummingbird HostExplorer emulator, menu and toolbar operations in the emulator window are disabled.
Workaround: Stop recording, select the required menu item or click the required toolbar button, and continue recording.
- When using an emulator that supports HLLAPI, closing the emulator window while recording may cause unexpected results.
Workaround: Stop recording before closing the emulator window.
- Clicking, typing or moving objects in the terminal emulator window while QuickTest is running a test or component may cause unexpected results.
Workaround: Wait until the end of the test or component or pause the test or component execution before using the emulator.
- The QuickTest Professional Terminal Emulator Add-in does not support recording operations on toolbar objects in terminal emulator applications.
Workaround: Record on the corresponding menu command for the toolbar button. Alternatively, you can use low-level recording to record operations on toolbars. For more information about low-level recording, refer to the HP QuickTest Professional User's Guide.
- When using the SendKey method to unlock a terminal emulator, for example, TeWindow("TeWindow").TeScreen("screen5296").SendKey TE_RESET, some emulators (such as Host On-Demand) may not be unlocked.
Workaround: Specify the keyboard event to send for the RESET command, using the Tools > Options > Terminal Emulator > Adjust Configuration > Run Settings > Run steps containing special emulator keys using keyboard events > Keys for RESET function option.
- If you record a test or component using one terminal emulator, it may not run correctly on another terminal emulator. For example, tests recorded on RUMBA may not run on IBM PCOM.
Terminal Emulators—Limitations
- You may experience unexpected behavior after you install an EXTRA! emulator. You may not be able to run QuickTest Professional or various features may stop working. This happens because the EXTRA! installation may have copied and registered an outdated version of the atl.dll file on your computer.
Workaround: Locate the atl.dll in your system folder (WINNT\system32). Its version should be 3.0 or higher. Register it with the regsvr32 utility.
- HostExplorer has a bug in the HLLAPI GetKey function. As a result, QuickTest will stop recording terminal emulator keyboard events after recording for a while, and the emulator might stop responding to keyboard events.
Workaround: Contact Hummingbird customer support to get the patch that fixes the problem with the HLLAPI GetKey function (where it stops responding after several calls).
- In order to record and run tests or components on Hummingbird 9.0 5250 sessions, you need to install a patch for Hummingbird.
Workaround: Contact Hummingbird customer support to get the patch that fixes the problem with HLLAPI where all 5250 fields appear protected.
- When working with Attachmate Terminal Viewer 3.1 5250 session, all the fields that appear on the screen before the first unprotected field are recognized as a single field.
- QuickTest may not recognize a TeField object in a NetManage RUMBA session immediately after installing the emulator.
Workaround: Restart your computer after installing RUMBA, even if the installation does not request a restart.
Connecting and Disconnecting
- If you have more than one terminal emulator session open, QuickTest does not recognize either session.
Workaround: While recording or running your test or component, make sure that only one terminal emulator session is connected at a time.
- If your test or component contains steps that disconnect the current emulator session during the run session, followed immediately by a TeScreen.Sync command, the test or component run might halt or take a long time to respond.
Workaround: Remove the Sync command from the test or component, or replace it with a Wait statement. For more information, refer to the Utility section of the HP QuickTest Professional Object Model Reference.
- Inserting a checkpoint, creating a new test or component, or opening an existing test or component when the emulator session is busy may cause unexpected problems.
Workaround: Check the connection status of your emulator on the status line of the emulator screen before performing any of these operations.
- You may experience unexpected behavior after disconnecting from a Host On-Demand session while recording.
Workaround: Stop recording before disconnecting from the session. Then, manually add a step that disconnects from the session.
- You may experience unexpected behavior if the terminal emulator is closed while QuickTest is recording.
Identifying Object
- By default, QuickTest uses the attached text and protected properties in TeField test object descriptions. If the attached text for a field changes from session to session, QuickTest cannot find the field during the run session.
Workaround: Open the Object Repository dialog box or the Object Properties dialog box for the object. Remove the attached text property from the field's description and add another property (or properties) such as start row, start column, or index to uniquely identify the object.
Tip: You can also create a smart identification definition for TeField objects so that your recorded test or component can run successfully even if the attached text property value for a particular TeField object changes. (Choose Tools > Object Identification > Enable Smart Identification and click Configure.) For more information on Smart Identification, refer to the HP QuickTest Professional User's Guide.
- You cannot use the label property in a programmatic description of the TeScreen object. However, since only one screen can exist in the given TeWindow at any one time, you can use TeScreen("MicClass:=TeScreen").
For example:
TeWindow("short name:=A").TeScreen("MicClass:=TeScreen").TeField("attached text:=User", "Protected:=False").Set "33333"
- The TeTextScreen properties current column and current row are available only for emulators that support HLLAPI.
- The location property is not recorded for TeField objects.
Workaround: Use the index property instead.
Visual Basic Applications—Creating and Running Tests and Components »
- When working with the Visual Basic Add-in, it is recommended to choose the Record and run on these applications (opened on session start) option and then to specify the application name in the Windows Applications tab of the Record and Run settings dialog box.
If you choose the Record and run test on any open Windows-based application option, you should open the Visual Basic application after the first time you start recording.
- Combobox objects of style Simple Combobox are not supported.
Web Objects—Creating and Running Tests and Components »
- If you record drag and drop steps on a Web element within the same frame, the test steps may fail during the run session if the screen resolution is not identical to the screen resolution during the recording session. This is because the target location coordinates may be different for different screen resolutions.
Workaround: If this problem occurs, adjust the Drop coordinates according to the new location.
- QuickTest Professional records changes in the edit field only on <input type="file"> tags. Browsing operations are not recorded.
- Clicks on form tags of type POST may not run correctly.
Workaround: If this problem occurs, change the ReplayType before the click to Run by mouse operations using: Setting.WebPackage("ReplayType") = 2. It is recommended to return the replay type to the default (Run by Events) setting after the click step: Setting.WebPackage("ReplayType") = 1.
- If you record on the AutoComplete dialog for password fields using the Tab key, QuickTest Professional may record incorrectly.
Workaround: Press Enter after entering the user name or click the button for logging in.
- When working with Web objects, if a property defined for a Description object is not supported (for example, the property name is misspelled), the property name is not ignored. Therefore a <WebObject>.ChildObjects statement using that Description object will fail.
- In previous releases, when you learned the objects on a Web page or ran a Page.ChildObjects step on a page with embedded hierarchies, (containing objects such as JavaApplets, ActiveX controls, or .NET Windows Forms controls), only the Web elements on the page were returned.
The Learn behavior has now changed such that when you learn all objects on a page, objects from the embedded hierarchies are also learned. However, the behavior of the ChildObjects method continues to retrieve only the Web objects, in order to preserve backward compatibility.
- Tabbed browsing is supported only in the English version of Microsoft Internet Explorer, Netscape Browser, and Mozilla Firefox. Additionally, tabbed browsing is not supported in Netscape 8.1.3.
- When QuickTest opens a browser, it may not correctly recognize multiple tabs that were opened and saved from a previous browser session.
Workaround: If multiple tabs are required, open them during the run session by adding the relevant steps to your test or component.
Running Tests or Components in Internet Explorer
- When Windows Live Toolbar is installed on Microsoft Internet Explorer 6.0 and tabbed browsing is enabled, QuickTest may display an error message every time you open Internet Explorer 6.0.
Workaround: Disable tabbed browsing in Microsoft Internet Explorer 6.0 by clicking the Change Windows Live Toolbar Options button in the Windows Live Toolbar. Then, in the left pane of the displayed dialog box, click the Tabbed Browsing link and clear the Turn on Tabbed browsing check box.
- When working in Microsoft Internet Explorer 7.0, QuickTest always performs mouse operations on list objects using browser events (and not using the mouse), even if the Web device level replay or replay type option is configured to use mouse operations.
- When using Microsoft Internet Explorer 7.0, QuickTest cannot switch to tabs that are not visible on the tab-band without scrolling.
Workaround: Perform either of the following:
- If you record a click on an area of an image map that is not mapped to a URL in Microsoft Internet Explorer, QuickTest Professional will perform a click on the first mapped area of that map during the run session.
- QuickTest Professional does not record on customized toolbar buttons in Microsoft Internet Explorer. (It records only on the toolbar buttons that are displayed by default in the browser.)
- When working with Internet Explorer 7.0, QuickTest Professional may not recognize Web objects, even though the Web Add-in is installed and loaded.
Workaround: Check and modify your Internet Explorer 7.0 settings.
- Modify the Internet Explorer 7.0 security settings, if needed.
In Internet Explorer 7.0, choose Tools > Internet Options. In the Security tab, clear the Enable Protected Mode check box and click OK.
- Enable the BHOManager Class Add-on if it is disabled. (QuickTest installs this add-on in Internet Explorer 7.0. The BHOManager Class Add-on must be set to Enabled for QuickTest to interact with the browser and its objects.)
In Internet Explorer 7.0, choose Tools > Manage Add-ons > Enable or Disable Add-ons (or Tools > Internet Options > Programs tab > Manage add-ons button if the Manage Add-ons menu item is not listed). In the Manage Add-ons dialog box, click the BHOManager Class to highlight it. Then, in the Settings area, click the Enable radio button and click OK.
- QuickTest Professional does not record on the Search frame of the Microsoft Internet Explorer browser.
- QuickTest Professional does not record on the Find window of the Microsoft Internet Explorer browser.
- QuickTest Professional may respond slowly during a recording session, if the drop-down boxes in a Web page contain a lot of data.
Workaround: Learn the objects on a Web page that contains a lot of data (instead of recording).
- During a run session, if two tabs with the same title but different page content are open simultaneously in the browser, QuickTest may erroneously activate the other tab, even though it correctly performs operations on the correct tab.
Workaround: Perform any of the following to correct this issue:
- During a run session, if the Close method is performed on a tab that has the same title as another tab in the open browser, QuickTest will close all the tabs with this title.
Running Tests or Components in Netscape Browser or Mozilla Firefox
- QuickTest Professional does not support the Netscape Browser menu.
- The .Object property for Web objects is not supported for Netscape Browser or Mozilla Firefox in this version of QuickTest.
- QuickTest Professional cannot run tests or components on Netscape Browser when Netscape Browser is in minimized mode.
- The Object Spy and Checkpoint Properties dialog boxes do not retrieve the current value of edit boxes in Netscape Browser and Mozilla Firefox dialog boxes.
- The Type property of the WebButton test object has a different default value in Microsoft Internet Explorer and Netscape Browser or Mozilla Firefox. In Microsoft Internet Explorer the default value is Button, but in Netscape Browser or Mozilla Firefox the default value is Submit.
Workaround: Do not use the Type property in the description of a WebButton test object.
- Standard checkpoints on links are not supported for running on Netscape Browser or Mozilla Firefox.
- If two minor versions of Mozilla Firefox are installed on the same computer, and the earlier version (for example, Firefox 1.5.0.3) was installed after the later version (for example, Firefox 1.5.0.8), QuickTest may not recognize which is the latest version.
Working with Microsoft Windows Vista
- The security settings in Microsoft Windows Vista may prevent you from performing a QuickTest Professional-related installation, such as a patch installation, or connecting to a Quality Center project (either directly or from QuickTest Professional). This can occur when the UAC (User Account Control) option in Windows Vista is set to ON, and you have not yet connected to a Quality Center project (if relevant).
Workaround: Temporarily turn off the UAC option, as follows:
- Log in to Windows Vista as an administrator.
- From the Control Panel, choose User Accounts > Change Security Settings.
- Clear the Use User Account Control (UAC) to help protect your computer check box and click OK.
After disabling the UAC option as described above, perform the required installation or connect to Quality Center as usual. When you are finished, you can turn the User Account Control (UAC) option on again. Hereafter, you should be able to connect to Quality Center, as needed.
- Due to a problem opening DCOM permissions on Windows Vista, QuickTest does not run properly on a remote Windows Vista host from Quality Center.
Workaround: Run RmtAgentFix.exe from the <QuickTest installation>\bin folder, or use the use the Additional Requirements Utility, which you open by choosing Start > Programs > QuickTest Professional > Tools > Additional Installation Requirements.
- On Windows Vista, QuickTest Professional seat licenses may not work correctly if you are not logged on as an administrator. (Note that concurrent licenses work as usual.)
Workaround: On Windows Vista, install QuickTest Professional and any QuickTest add-ins as an administrator. To do this, right-click setup.exe from the root folder of the QuickTest Professional installation DVD and choose Run as administrator.
Then, every time you open QuickTest, open it as an administrator. To do this, right-click the QuickTest Professional icon on your desktop and choose Run as administrator.
- QuickTest Professional does not support the recording of operations on the Start menu of Windows Vista (except for Start > Run).
Workaround: Manually add a step in your test to open the required application.
Note: For additional Windows Vista issues, see:
Text Recognition Support for Windows-Based Environments
- In recent versions of QuickTest Professional, text-capturing test object methods, reserved object methods, text/text area checkpoints, and text/text area output value steps were not available for objects in Windows-based environments.
You can use the text and text area checkpoint or output value commands to verify or retrieve text in 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 tries to retrieve the text directly from the object using a Windows API-based mechanism (default mechanism). If QuickTest cannot capture the text this way (for example, because the text is part of a picture), it tries to capture the text using an OCR (optical character recognition) mechanism provided by ABBYY Software Ltd.
You can change the default behavior, if needed, 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.
Note: Although these text-capturing options and methods are now 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 it's text (or similar) property.
For more information, refer to the relevant sections in the HP QuickTest Professional User's Guide, and search for the GetText, GetVisibleText, and GetTextLocation methods in the relevant sections of the QuickTest Object Model Reference Help.
- Sometimes the default OCR settings result in additional unexpected characters in the captured text.
Workaround: Try one or more of the following modifications:
- On Windows Vista 32-bit or any 64-bit operating system, QuickTest text recognition features (such as text checkpoints and output values, GetVisibleText and GetTextLocation test object methods, and TextUtil.GetText and TextUtil.GetTextLocation reserved object methods) are limited and are not always reliable.
Workaround: On Windows Vista, you can improve text recognition by applying the Classic Windows theme and by setting the text recognition mode to Use only OCR in QuickTest. (You can do this by choosing Tools > Options, and then, in the General tab, selecting Use only OCR from the Use text recognition methods in this order box.)
- If a "windowless" ActiveX radio button object is not first activated by clicking on it (AcxRadioButton.Click) or by using the Set method, a step containing the AcxRadioButton.GetVisibleText method will return an error stating that the object is not visible.
Workaround: Insert a step using the Click or Set methods prior to any step that uses the GetVisibleText method on a "windowless" ActiveX radio button object.
Active Screen
- When recording on WinMenu objects, the Active Screen is not captured.
- When the Active Screen displays a Java applet or ActiveX control within a Web page, the applet or control is for viewing purposes only and you cannot perform operations (for example, create checkpoints, add methods, and so forth) on the object.
Workaround: Record an operation on the Java applet/ActiveX control to create a step on the object with the ActiveX Add-in and/or Java Add-in (available separately) loaded. Then you can create a checkpoint, parameterize a step, or add a method from the individual Java applet/ActiveX control in the Active Screen.
SAP Windows-based Applications—Using the Active Screen »
- Active Screen images are based on captured screen bitmaps. Therefore, objects that are not visible in the SAP GUI for Windows view are not part of the Active Screen image. You cannot add objects to the script from the Active Screen if they were not in the captured view.
- Drop-down menus are not captured in the Active Screen. Active Screen technology captures the data after the menu is closed and the menu item is selected.
- While recording, QuickTest Professional captures one Active Screen image for several steps. QuickTest Professional records steps only when the SAP GUI for Windows client sends information to the SAP back-end server. When this occurs, all steps that were performed between the previous communication and the current one are added to the script. The last screen that was sent to the server is captured by the Active Screen for all steps recorded during that communication.
- When recording on Web elements inside SAP Gui for Windows applications, HTML images are not captured.
- Adding objects to the object repository (using the View/Add Object option, or creating checkpoint or output value steps) from an Active Screen created from a step recorded on a Web element inside a SAP Gui for Windows application generates an incorrect object hierarchy in the object repository.
SAP Web-based Applications—Using the Active Screen »
- The Active Screen may not display the entire HTML page captured while recording your test.
Workaround: Resize the Active Screen so that it best fits the HTML page size.
- When testing an SAP Enterprise Portal application, it is recommended to set advanced authentication for Active Screen access (Test > Settings > Web). For more information, refer to the HP QuickTest Professional User's Guide.
- Avoid using an Active Screen that was captured when a pop-up dialog was open to add an object from the main window to the object repository. Doing this results in an incorrect object hierarchy in the object repository.
Automation
- When running an object repository automation script, if the object returned after calling a RepositoryUtil.GetChildren statement is not nulled, QuickTest crashes at the end of the script.
Workaround: Add the following line to the end of the script:
TestObject = NULL
where the TestObject variable is the test object returned by the GetChildren method.
- Using an automation script to open a test created using QuickTest 8.2 or earlier may take some time since the test is automatically converted to the current QuickTest format. Note that when opening a test in this way, you cannot choose whether or not to convert it. Tests are automatically converted to the new format and cannot be opened in earlier versions of QuickTest after they have been converted and saved.
- The SetObjectRepositoryAsDefault method and ObjectRepositoryPath property path are no longer supported.
Workaround: Update your automation scripts to use the methods and properties of the ObjectRepositories collection instead. For more information, refer to (Help > QuickTest Professional Help > QuickTest Advanced References > QuickTest Automation).
Data Table
- If you import a Microsoft Excel table containing a combo box or list cells, conditional formatting, or other special cell formats, the formats are not imported and the cells are displayed in the Data Table with fixed values.
- Entering a very large number in the Data Table may cause unexpected behavior.
Checkpoints and Output Values
General—Checkpoints and Output Values »
- Checkpoints that contain more than 64K of data may run slowly.
- The Focused property in a checkpoint inserted while recording will always have the value False.
Workaround: Change the value of the property manually or perform an update run (Automation> Update Run Mode) on the test or component.
- Checkpoints on page source/HTML tags cannot be inserted from the Active Screen and must be inserted while recording. These checkpoints may fail during the first run session.
Workaround: Perform an update run (Automation> Update Run Mode) of your test or component before you run a test or component that includes a page source/HTML tag checkpoint.
- If you insert checkpoints from the Active Screen when you are working with an application containing a browser control rather than with a Web browser, your checkpoints may fail.
Workaround: Insert checkpoints while recording.
- When inserting a checkpoint from the Active Screen on a VbComboBox object that checks the sellength or seltext property, the captured value may be incorrect.
Workaround: Update the value manually.
- Checkpoints are not supported for WinComboBox objects of style Simple Combobox.
- When you create a standard checkpoint for a Calendar control (for WinCalendar, AcxCalendar, and SwfCalendar test objects), the Date and Time properties are not selected by default.
- For database checkpoints, the format of captured values varies depending on the specific system settings. For example, date and time values may be set to different formats.
Workaround: If you are running the test or component on a different system than the one you used to record the test or component, confirm that the systems use the same format settings.
- When you create a database checkpoint on one machine and try to run it on different machine, you should have the same ODBC driver installed on both machines.
ActiveX—Checkpoints and Output Values »
- ActiveX table checkpoints capture only visible rows in data bound grids.
- When you insert a checkpoint on an ActiveX table from the Active Screen, the browser (or application) must be open to the same page (or screen). Otherwise, some data from the ActiveX table will be missing.
Workaround: Create ActiveX table checkpoints while recording.
- Checkpoints and output values for ActiveX properties of type VT_DISPATCH are not supported.
- Checkpoints and output values for write-only ActiveX properties are not supported.
- If you perform an update run (Automation > Update Run Mode) on a test that contains checkpoints or output values for windowless ActiveX controls, and then you rerun the test, the run session may fail. This is because a hidden property called "windowless" is missing from the test object description.
Workaround: You can either relearn the problematic ActiveX controls, or you can add the "windowless" property with a value of 1 to all problematic, windowless ActiveX controls.
Java—Checkpoints and Output Values »
- You can create text checkpoints and text output values only for Java objects that meet specific criteria. For more information, refer to the HP QuickTest Professional Add-ins Guide.
- To create a new table checkpoint on a Java table while editing a test or component, you must first open the application containing the table you want to check and display the table in the application.
- If you add a checkpoints on a JavaList or JavaTree object while editing a test or component, the list_content or tree_content property is not available in the checkpoint.
Workaround: Create checkpoints on Java lists and Java trees during a record session.
Workaround: If a checkpoint on a transient object is required, make sure the object is visible prior to executing the checkpoint. For example, in the case of combo box list, you should insert a statement that clicks on the combo box button before executing the checkpoint.
.NET Web Forms—Checkpoints and Output Values »
- Text checkpoints are not supported for WbfTreeView, WbfToolbar, and WbfTabStrip objects.
- The Active Screen image for a WbfCalendar object is always saved before navigation. For example, if you click a NextMonth link, the Active Screen displays the current month. Therefore, if you create a checkpoint from the Active Screen and insert it after the Calendar.ShowNextMonth line, the checkpoint will fail.
Workarounds:
Insert checkpoints on calendar objects while recording.
Or
While editing your test, edit the expected value for the checkpoint or insert the checkpoint before the current step.- Table checkpoints are supported for WbfUltraGrid objects only while recording.
- When using the WbfUltraGrid.RowCount and WbfUltraGrid.ColumnCount methods or performing a table checkpoint on a grid that also contains additional grid controls inside it, QuickTest retrieves the rows or columns only for the outermost table. Note that the rows property and RowCount method count only the non-grouping rows.
Oracle—Checkpoints »
Workaround: If a checkpoint on a transient object is required, make sure the object is visible prior to executing the checkpoint. For example, in the case of combo box list, you should insert a statement that clicks on the combo box button before executing the checkpoint.
SAP—Checkpoints and the Object Spy »
- It is recommended that you record a step that results in communication with the server (such as pressing Enter) before inserting a checkpoint or output value, to ensure that the correct object properties are captured with your checkpoint.
- You cannot use the Object Spy or create checkpoints for the controls listed below. However, you can successfully record and run steps on them.
- Creating checkpoints or using the Object Spy on an object that is located in a currently inactive SAP screen (i.e. the screen is behind an invoked dialog box) is not supported. However, you can create checkpoints on status bar messages (displayed in an inactive window) using the Record status bar messages option (Tools > Options > SAP > Record status bar messages).
- When running old 6.20 tests on the 6.40 client, checkpoints on radio buttons, check boxes, edit boxes, or regular buttons may fail due to changes to tooltip property values for these objects in the 6.40 client.
- QuickTest can estimate the number of rows in a table control, but it cannot retrieve the exact number because only the table content that is visible on the client is actually available. Data from non-visible rows are stored only on the back-end server. Therefore, when inserting or modifying checkpoints for a table control object, the number of rows specified in the Define/Modify Row Range dialog box may not be accurate.
- Although it may take a while to insert a table checkpoint for large tables, it is recommended not to perform any operations on the SAP GUI window while QuickTest is retrieving the necessary data for the checkpoint. Changing the transaction state or navigating to another window, for example, while QuickTest is retrieving information for the checkpoint, may cause severe problems.
- When inserting a checkpoint on a table or grid from the Active Screen, you must have the actual table open in your SAP Gui for Windows application to extract the correct information from the table or grid.
Siebel—Checkpoints and the Object Spy »
- To create a table content checkpoint or output value for the appropriate object type (for example, SiebList, SiebPicklist, or SiebPageTabs) when editing your test or component, you must open the application to the exact screen in which the object appears. Otherwise, only the Properties tab is displayed in the Table Checkpoint dialog box or Table Output Value dialog box.
- Checkpoints created for SiebList objects that contain a Total row may fail during a run session if the action that led to the update of the Total row was not recorded.
- The Object Spy and checkpoints identify expanded calculator and calendar popup objects as Window("Siebel control popup").
Terminal Emulators—Checkpoints and Output Values »
- In some cases, a bitmap checkpoint on a TeScreen may fail because the cursor shows in the expected bitmap, and not in the actual bitmap (or the other way around).
Workaround: Set the emulator cursor to a slow blink rate, or not to blink at all. This enhances the probability that the cursor is not captured in the bitmap.
Web Services—Checkpoints and Output Values »
- If you create a checkpoint or output value step for an operation that returns a multi-dimensional array (or perform an update run on such a step), the XML tree is generated for only one dimension of the array.
- When running existing tests, checkpoints checking complex values may fail if the following conditions are met:
- The checkpoint was created using the QuickTest Professional Web Services Add-in 9.1.
- The WSDL on which the WebService test object is based uses RPC-literal encoding.
- The test object was learned using the .NET 2.0 WSE toolkit.
This is due to the fact that the old mechanism for creating checkpoints on this type of WSDL created an unnecessary element with an empty value. The new mechanism does not create this element for checkpoints and does not capture this element during the run session.
Workaround: Do one of the following:
- Perform an update run (Automation> Update Run Mode) of tests containing checkpoints matching the above description.
- Recreate the relevant checkpoints in QuickTest.
- Open the Checkpoint Properties dialog box and clear the check box next to the problematic elements.
XML—Checkpoints and Output Values »
- When executing an XML checkpoint on an XML file that contains > as a value, an error message may occur.
- When you add a new value node to an XML node, in some cases the new value may not be displayed.
Workaround: Close the Edit XML as Text dialog box and reopen it to display the new value node correctly.
- When inserting an XML file checkpoint on a file that cannot be loaded, or a file that is formatted incorrectly, you may receive an error message.
- Creating and running XML checkpoints for large XML documents may take a few minutes.
Object Repository
- If you modify the name of a test object in the Object Repository while your test or component script contains a syntax error, the new name is not updated correctly within your test or component script.
Workaround: Clear the Automatically update test and component steps when you rename test objects check box (Tools > Options > General tab) and perform the renames in the script manually (recommended) or solve the syntax error, and then close and reopen the document in QuickTest to display the renamed objects in your steps.
HP Screen Recorder
- When using the Screen Recorder on Windows Vista, setting the Window's display settings to the Classic Windows theme may improve performance.
- Record and run session performance may be affected adversely when using the Screen Recorder on a computer running Windows Vista 32-bit or any 64-bit operating system. This is because some capture drivers (such as Blueberry or ASUS' Enhanced Display Driver) cannot be installed on these operating systems. Note that if you try to install the capture driver from the Screen Recorder Options dialog box while working on one of these operating systems, an error message is displayed.
- When a Quality Center client is installed on the same computer as QuickTest Professional, uninstalling QuickTest Professional may remove the association of movie (FBR) files. This may prevent you from viewing movies associated with defects in Quality Center using the HP Micro Player.
Workaround: Re-associate the movie files with the HP Micro Player, as follows:
- When using the Screen Recorder on Windows Vista to save all results to the Test Results, QuickTest may run very slowly or hang.
Workaround: If this occurs, disable the Screen Recorder.
QuickTest Professional Documentation
- All Help topics under the VBScript Reference > VBScript, VBScript Reference > Script Runtime, and VBScript Reference > Windows Script Host sections are from Microsoft. These Help files were not prepared by HP and HP is not responsible for their content. These help files were taken directly from the Microsoft Script56.chm help file, downloaded from: http://msdn2.microsoft.com/en-us/library/sx7b3k7y.aspx
The information under the VBScript Reference heading may contain errors, problems, or other limitations. HP makes no representations whatsoever as to the accuracy, adequacy, reliability, currentness, completeness, suitability or applicability of the information under the VBScript Reference heading. HP is not responsible for any damages, including the loss of time, which may result from using the information in the help files under the VBScript Reference heading.
- The Previous buttons on Help topic pages may not display the expected page.
Workaround: Use the table of contents, index, or search to find the topic you need.
- When Mozilla Firefox is the default browser, the Readme files for installed patches cannot be directly viewed by clicking the relevant links from the Product Information page.
Workaround: Save the patch Readme file locally and open it with Microsoft Internet Explorer or with any text viewer.
- On some computers, links from a PDF to an external Web site (for example, http://www.adobe.com) do not work.
Workaround: Manually navigate to the required Web site.
Quality Center Integration and Business Process Testing
The Business Process Testing issues described below relate to working with business components and business process tests in QuickTest. For information on issues related to working with business components in Quality Center, refer to the Quality Center Readme.
For Business Process Testing, QuickTest Professional integrates with Quality Center version 9.0 and later (with a license for Business Process Testing support).
- Quality Center is not Unicode compliant. Therefore:
- When working with tests or components stored in Quality Center, you should not use Unicode values (such as the name of the test or component, the name of an application area, the default value of a test, action, or component parameter, method argument values, and so forth).
- Data that is sent to QuickTest from Quality Center (such as values for test, action, or component parameters) is not Unicode compliant.
- QuickTest results containing Unicode characters may appear corrupted in the Quality Center result grid. You can, however, open and view results containing Unicode characters in the QuickTest Test Results window.
- Before opening or running a test or component from Quality Center, you must open the current installation of QuickTest at least once. Otherwise, Quality Center may not be able to open QuickTest.
- If you modify checkpoint or output settings for a component from the Object Repository dialog box or the Object Repository Manager, you will not be able to view the details of that checkpoint or output value from Quality Center.
Workaround: In the Keyword View, open the Checkpoint Properties or Output Value Properties dialog box to modify the checkpoint and output value settings for components.
To solve the problem for a checkpoint or output value that has already been edited in the Object Repository dialog box or the Object Repository Manager, ensure that the checkpoint or output object is saved in the local object repository (so it is editable). Then, in the Keyword View, modify the checkpoint or output value in the Checkpoint Properties or Output Value Properties dialog box, and save those changes.
- Before using the Business Component Upgrade Tool (Start > Programs > QuickTest Professional > Tools > Business Component Upgrade Tool), you must open the current installation of QuickTest at least once. Otherwise, the Business Component Upgrade Tool may not be able to open QuickTest.
- Renaming a QuickTest test or component from Quality Center may cause the test or component to behave unexpectedly.
Workaround: To rename a test or component, open it in QuickTest and rename it using the Save As option. If the test or component has already been renamed from Quality Center, use the rename option again to restore the old name, and then use the Save As option in QuickTest. Renaming a QuickTest test parameter from QuickTest will cause any run-time parameter values already set for this parameter in Quality Center to be lost.
- When working with Business Process Testing, you should not work with the same business component in Quality Center and QuickTest simultaneously on the same computer. Doing so may corrupt that business component.
- When running business process tests with a large number of iterations and business components, you may encounter memory availability problems after some time.
Workaround: Use the Restart testing tool after __ runs option in the Remote Agent Settings dialog box (Start > Programs > QuickTest Professional > Tools > Remote Agent) to count the number of business components being run and automatically restart QuickTest at the end of the first business process test iteration reached after passing the defined threshold.
- If you created a business component in QuickTest 8.2.x without an associated application area, then when you open it in QuickTest 9.0 or later and choose to convert it to the current format, any customized business component settings are cleared, and therefore the business component run will fail.
Workaround: After converting the business component, you must associate it with an application area that contains the required resources and settings.
LoadRunner and Business Process Monitor Integration
- LoadRunner run-time settings are not relevant for QuickTest GUI Vusers. Any required settings must be defined in the QuickTest test settings. When using the LoadRunner Scheduler, the number of passed iterations shown in the Vusers window of the LoadRunner Controller is inaccurate.
- QuickTest SAP GUI Vusers are not supported by LoadRunner.
- External QuickTest resources can be used either by defining them in the QuickTest test with an absolute path or by adding them as supplementary files and transferring them to Load Generator in the QuickTest test folder.
Multilingual Support
Overview »
- QuickTest Professional is Unicode compliant and supports multilingual environments and applications with the following exceptions:
- Names and paths of tests, components, application areas, and resources (for example, function libraries, object repositories, and recovery scenarios) are not Unicode compliant and therefore should be specified either in English or in the language of the operating system.
- Quality Center is not Unicode compliant. For specific details, see Quality Center Integration and Business Process Testing.
Software Support »
- You can access the HP Software Support Web site at: http://www.hp.com/go/hpsoftwaresupport
Useful Information »
- You can download the Microsoft Debugger for far-eastern Windows operating systems from Microsoft's Windows Script Technologies site:
- Chinese Windows. http://www.microsoft.com/china/scripting
- Japanese Windows. http://www.microsoft.com/japan/msdn/scripting/default.asp
- Korean Windows. http://www.microsoft.com/korea/scripting
Known Problems and Limitations »
Text Recognition in Multi-Lingual Environments
- When working with CJK (Chinese, Japanese, or Korean) characters on Windows Vista 32-bit or any 64-bit operating system, QuickTest text recognition features (such as text checkpoints and output values, GetVisibleText and GetTextLocation test object methods, and TextUtil.GetText and TextUtil.GetTextLocation reserved object methods) are limited and are not always reliable. For more information, see Text Recognition Support for Windows-Based Environments.
Workaround: Display the fonts for these languages at 22 points or higher.
Recording and Running Tests and Components
- QuickTest may behave unexpectedly when using multi-byte string inputs if it is installed on a VMware operating system.
Workaround: Set the hardware acceleration of the display driver to None. If this does not work, uninstall the VMware display adapter.
- Manually editing scripts in the Expert View using the Korean language on Windows XP or Windows 2003 operating systems may cause QuickTest to malfunction.
Workaround: Choose Control Panel > Regional and Language Options > Languages tab > Details > Advanced tab and select the Turn off advanced text services check box.
Note that you may need to restart your computer after setting this option.
- There may be cases during a run session when QuickTest loses the focus of the application you are testing when working in a Korean, Chinese, or Japanese operating system. This may result in a loss of data during the run session.
Workaround: Run an Activate method on the application's window to ensure focus on the window before performing the next step. For example:
Window("Notepad").Activate
- Low-level recording mode is not fully supported for multibyte character input.
- When using Chinese IME to record multiline objects:
- Running the Type method on computers with Japanese, Korean, or Chinese operating systems may not work as expected.
Workaround: Add an English input locale to the computer (using the Regional Options or Regional and Language Options in your Control Panel).
- Multibyte punctuation symbols and other multibyte special characters, such as multibyte question marks, multibyte spaces, and multibyte brackets, should not be used when naming tests, components and application areas.
Running Tests or Components in Netscape Browser
Running Tests or Components in Mozilla Firefox
Support for Web Objects
Third-Party License Agreements
ABBYY® FineReader® Engine 8.0 © ABBYY Software LLC. 2004. ABBYY FineReader - the keenest eye in OCR.
ABBYY, FINEREADER and ABBYY FineReader are either registered trademarks or trademarks of ABBYY Software Ltd.
SlickEdit® is a registered trademark of SlickEdit Inc.
============================================
For the QuickTest Professional Web Services Add-in only:
===========================================================
NOTICE file corresponding to section 4(d) of the Apache License,
Version 2.0, in this case for the Apache Axis distribution.
===========================================================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
HP Support
You can visit the HP Software Support Web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support site to:
- Search for knowledge documents of interest
- Submit and track support cases and enhancement requests
- Download software patches
- Manage support contracts
- Look up HP support contacts
- Review information about available services
- Enter into discussions with other software customers
- Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jspTo register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.htmlLegal Notices
© Copyright 2002 - 2008 Mercury Interactive (Israel) Ltd.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Adobe® is a trademark of Adobe Systems Incorporated.
Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft® and Windows® are U.S registered trademarks of Microsoft Corporation.
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.
| © Copyright 2008 Mercury Interactive (Israel) Ltd. |