Obtaining the Latest Release Notes
System Requirements
What's New
Technical Notes
Known Issues
Contacting Compuware Customer Support
If you accessed this document from the product CD or from the program shortcuts on your desktop, you may not be reading the latest release notes. For the most recent information, go to FrontLine, Compuware's technical support web site. The first time you access FrontLine, you are required to register and obtain a password. After logging onto FrontLine, select your product from the drop-down list and click Go. On the left side of the page, click the Documentation link. You will find the latest release notes listed with the other product documentation.
TestPartner has the following minimum system requirements:
TestPartner supports the following IMEs for the listed input systems.
Legend
X - Supported
|
|
|||||
|
Japanese Input System |
Description |
Name |
Windows 2000 |
Windows XP |
Windows 2003 |
|
|
MS-IME2000 |
imejp.ime |
X |
X |
X |
|
|
MS-IME2002 |
imjp81.ime |
|
X |
X |
|
|
MS-IME2003 |
imjp9.ime |
|
X |
X |
|
|
|
|
|
|
|
|
|
|||||
|
Korean Input System |
Description |
Name |
Windows 2000 |
Windows XP |
Windows 2003 |
|
|
MS-IME98 |
imekr98u.ime |
X |
|
|
|
|
IME 2000 |
imekr61.ime |
|
X |
X |
|
|
|
|
|
|
|
|
|
|||||
|
Simplified Chinese Input System |
Description |
Name |
Windows 2000 |
Windows XP |
Windows 2003 |
|
|
QuanPin |
winpy.ime |
X |
X |
X |
|
|
MS-PinYin98 |
pintlgnt.ime |
X |
X |
|
|
|
MS-PinYin
3.0 |
pintlgnt.ime |
|
X |
X |
|
|
NeiMa |
wingb.ime |
X |
X |
|
|
|
ZhengMa |
winzm.ime |
X |
X |
X |
|
|
ShuangPin |
winsp.ime |
X |
X |
X |
|
|
WuBi86 |
winwb86.ime |
X* |
X* |
X* |
|
|
WuBi98 |
winwb98.ime |
X* |
X* |
X* |
|
|
Enhanced
Unicode |
surime.ime |
|
X* |
X* |
|
* Only appears with Windows XP and Windows Server 2003 with Office XP Multilingual Support complete install. |
|||||
|
|
|
|
|
|
|
|
|
|||||
|
Traditional Chinese Input System |
Description |
Name |
Windows 2000 |
Windows XP |
Windows 2003 |
|
|
Alphanumeric |
romanime.ime |
X |
X |
X |
|
|
Unicode |
unicdime.ime |
X |
X |
X |
|
|
Quick |
quick.ime |
X |
X |
X |
|
|
Phonetic |
phon.ime |
X |
X |
X |
|
|
New
Phonetic |
tintlgnt.ime |
X |
X |
X |
|
|
New
ChangJie |
cintlgnt.ime |
X |
X |
X |
|
|
DaYi |
dayi.ime |
X |
X |
X |
|
|
ChangJie |
chajie.ime |
X |
X |
X |
|
|
Big5
Code |
winime.ime |
X |
X |
X |
|
|
Array |
winar30.ime |
X |
X |
X |
Notes:
TestPartner 5.6.0 provides full object recognition, capture, and playback support for Oracle 11i E-Business Suite applications. This includes an Oracle playback timing setting to facilitate proper synchronization when playing back test applications.
TestPartner 5.6.0 includes an unattended installation option which you can use to perform multiple installations of TestPartner from a remote location. Additionally, you can customize the installation, modify existing installations, or remove existing installations.
TestPartner 5.6.0 supports SQL Server 2000 transactional replication. With transactional replication, you can push data and database objects from a central TestPartner master database to multiple distributed databases. In addition, you can schedule the distribution of data modifications at regular intervals to customize the time lag between updates and the required connection time of participating databases.
TestPartner 5.6.0 provides suggested practices for improving Web and SAP Application playback performance. For Web applications, you can modify test scripts and adjust playback settings to improve Web application playback performance. For SAP Applications, you can use the native recording capability of your SAP application and include the recorded results in a TestPartner script to improve playback performance.
TestPartner 5.6.0 provides suggested practices for using raw mode, a testing technique that includes using coordinate-based clicks and shortcut keys instead of using object recognition to test applications. Raw mode is useful for testing applications that contain highly customized controls or a graphical user interface which appears as a single control, such as those deployed and managed using Windows Terminal Services and Citrix Presentation Server.
TestPartner 5.6.0 provides new objects and methods to support Internet Explorer 7 features such as tabbed browsing and the Favorites Center. To expose these methods, use the following objects in TestPartner scripts:
Additionally, see the Help topic "Playing Back Existing Scripts in Internet Explorer 7" for tips on configuring Internet Explorer 7 to ensure proper playback of scripts recorded against a previous version of Internet Explorer.
TestPartner 5.6.0 can run in VMWare Workstation 5.5, Player 1.0, Server 1.0, and ESX/GSX Servers 3 provided the following requirements are met:
This section includes technical information that may affect how you use the product.
TestPartner 5.6.0 supports native database authentication, which requires the configuration of all database connections for use with TestPartner in addition to creating a Data Source Name (DSN). The configuration process consists of using the new Configure Data Source dialog box to perform the following tasks:
If you are upgrading from a TestPartner release prior to TestPartner 5.4.0 and currently using any of the following databases, you must configure your database connection prior to logging on to TestPartner.
For more information, click the Help button on the TestPartner Logon dialog box or access the "Configuring a TestPartner Database Connection" section in the Installation and Configuration Guide or in the TestPartner Help.
Manipulation of the TestPartner repository/database outside of TestPartner or the Database Maintenance Utility violates the TestPartner License Agreement and may lead to database corruption.
Data transmissions on WAN connections have higher latency than Local or Metropolitan Area Networks. If TestPartner connects to its database across a WAN, or is executed from an application server across a WAN, the latency may cause TestPartner to behave unreliably. Compuware does not recommend or support TestPartner if it connects to its back end database, which is located on a remote server, via a WAN. This applies only to TestPartner and its back end database. The application under test may be located anywhere, as long as it is supported by its architecture.
TestPartner 5.6.0 drops support for Oracle 8.1.7 or MSDE 1.0 as a TestPartner database repository.
The TestPartner Installation Guide contains detailed instructions on how to set up a database for TestPartner. However, there are additional instructions for creating new databases and updating database versions in the Getting Started section for Administrators in TestPartner Help. You may also need to refer to these instructions depending on your database setup.
TestPartner 5.6.0 ships with the Compuware License Administration Utility (LAU) 4.0, which uses License Manager 4.0. All TestPartner 5.6.0 licenses can only be set and configured using License Manager 4.0. Click the Install License Utility for TestPartner link on the product CD to install License Manager 4.0.
When selecting features to install during VSTS installation, the following components must be selected in the Microsoft Visual Studio 2005 Setup - Options Page to enable functional testing in VSTS using TestPartner:
After installing TestPartner on a computer containing Visual Studio .NET, Visual Studio may reconfigure itself when started. This is a result of the Visual Basic for Applications (VBA) 6.2 setup which is run during TestPartner's installation, and does not have any adverse affects on the computer.
If the IME mode changes during script recording and the IME state is different when recording is finished than it was when recording started, the IME state must be reset to its initial recording state before playback to ensure the recorded script plays back correctly. For example, if the IME mode is Kana when recording begins, but is then changed to Half-Width English during recording, the IME Mode must be set back to Kana before playing back the script. As with any application, IME mode must be in its original recorded state for a script that uses it to playback correctly.
When using a Traditional Chinese IME to input a character to a single line edit control in Java applications, a "candidate list" window displays possible choices of Chinese characters that can be input based on the characters being typed. To select a choice in the list, a number corresponding to the choice or the SPACE key must be pressed to select the choice. This inputs the choice to the single line edit control. However, for TestPartner to record the contents of the edit control correctly, the BACKSPACE key must be pressed to close the candidate list window of the IME if one is visible.
TestPartner supports single-byte and double-byte encoded characters available through GB18030. TestPartner does not support four-byte encoded characters available through GB18030.
The following factors may affect test record and playback performance in TestPartner:
TestPartner recording or playback may slow down when testing applications on slower speed machines when several hundred controls exist on one page.
TestPartner 5.6.0 supports SAP Web Application Server 6.20 (patch level 42 or higher) and SAP Web Application Server 6.40 (patch level 15 or higher). Users upgrading from SAP Web Application Server 6.20 to SAP Web Application Server 6.40 may experience performance degradation. When upgrading to SAP Web Application Server 6.40, make sure to use patch level 15 or higher. The performance issue is currently being investigated.
SAP eCATT users who want to use TestPartner as the extended testing tool of choice must use eCATT to perform initial external tool setup. Please refer to SAP eCATT documentation for SAP Web Application Server at http://help.sap.com. Open the appropriate Web Application Server Help, then search for the help topic "Using an External Tool with eCATT" for instructions on setting up an external testing tool for eCATT.
TestPartner requires server side scripting support to be turned on in SAP GUI for Windows 6.20 and SAP GUI for Windows 6.40 to identify, record, and playback SAP objects. SAP GUI for Windows scripting support is included in the installation by default. In the SAP application, select the Scripting tab in SAP options and ensure the Enable Scripting check box is selected. Also, clear the Notify when a script attaches to a running GUI check box to prevent a confirmation dialog box from displaying each time TestPartner records against an SAP application.
Additional SAP scripting requirements are outlined in the SAP document "SAP GUI Scripting Security Settings", which is available to authorized users of the SAP Service Marketplace on the SAP Support Portal at https://websmp206.sap-ag.de/support. To find the document, select the Advanced Search link and type "SAP GUI Scripting Security Settings".
Certain actions performed against SAP are executed from the SAP server. To execute these actions, SAP requires the communication object on the server. When the communication object is on the server, SAP blocks all scripting calls until the SAP communication object is on the client. This can happen when an eCATT script executed from the server tries to access its own SAP GUI session.
When this happens, TestPartner cannot record or playback against the SAP session. To work around this issue, create a new session (System>Create Session in SAP) or log out of SAP and log back in.
TestPartner scripts recorded against HTML controls in SAP ITS 6.10 and SAP ITS 6.20 may not playback properly. This is because the default properties used to record against HTML controls contain additional elements that cause indexing to be different upon subsequent script playback. To avoid playback issues for HTML controls in SAP ITS 6.10 and SAP ITS 6.20, create an attach name profile using the recommended properties as shown in the table below.
The recommended property settings for proper recording and playback of controls in SAP ITS 6.10 and 6.20 are as follows:
Control
|
Default Property
|
Recommended Property |
|
HTMLFrame |
Src,
Name |
ID |
HTMLSpan |
ID |
InnerText |
|
HTMLDIV
(required in some cases) |
ID or Parent
ID |
ElementID |
Note that these are recommendations only. There may be cases where the recommendations are not appropriate. It is also recommended that the Record Frame Resizing option in TestPartner's Advanced Record Options be set to No, which is the default setting.
TestPartner typically displays a progress bar to indicate a property check's capture progress against a control with a large child control hierarchy. This feature has been disabled for JavaMenu controls. Property checks can still be performed against any TJavaMenu control. However, the progress bar will not display to indicate the property check capture status. Wait until the Property Check setup window displays for the JavaMenu control before proceeding.
In TestPartner versions prior to TestPartner 5.4.0, the Left and Top coordinates of a cell retrieved by the GetCellBounds() method of a TDotNETDataGrid object were reversed. In TestPartner 5.4.0 and higher, this has been corrected and the coordinates return the correct values. Note that scripts recorded prior to TestPartner 5.4.0 that include these coordinates may not play back correctly.
This section describes known issues related to the current release of TestPartner.
The availability of Object Map entries is not limited to the Common project and the project in which they are saved. Object Map entires are available in any TestPartner project.
If two TestPartner assets with the same name belong to different TestPartner projects, using the $TPInclude statement to include them in the same script can cause a VBA error. The error occurs when attempting to open both assets. When this happens, TestPartner issues a message that indicates a VBA asset naming conflict has occurred, and that the asset window will be closed. When the error occurs, TestPartner removes the most recently loaded same named asset from memory.
The error occurs because of how VBA handles assets in its own projects. When two assets with the same name exist in a VBA project, VBA renames the most recently created same named asset by adding a "1" onto the end of the name. For example, if both assets are named MYMODULE1, VBA renames the second asset MYMODULE11. VBA only makes this change internally while the asset is loaded. The name of the asset does not change in the TestPartner database. VBA does not allow two assets with the same name to exist in the same project, so TestPartner issues an error.
The asset name can not be left as what VBA changed it to because that could break scripts with user forms and class modules, which refer to the name of the asset in the code. To work around this issue, do not give the same name to two assets if these assets will be included in the same script.
Due to limitations in VBA, Microsoft does not support arrays for .NET objects when the object's .NET assembly is referenced. As a result, arrays of .NET objects cannot be used with TestPartner object extension for .NET. Examining an object's array in a Locals window when the object's .NET assembly is referenced may cause TestPartner to stop responding.
Using Oracle ODBC driver versions 9.2.0.6.3 and 9.2.0.6.5 causes an error when logging in and creating a new script. The error is ORA-011459: INVALID LENGTH FOR VARIABLE CHARACTER STRING. To work around this issue, use Oracle driver version 9.2.0.5.4 or earlier. This is an Oracle issue. Please contact Oracle for resolution details.
For Oracle 9.0.1 and 9.2.0, Oracle database schema names for TestParter databases must not exceed seven characters.
Prior to TestPartner 5.4.0, .NET DataGrid controls with enum-based columns containing either non-consecutive numerical values or a numerical value of zero were captured incorrectly. This was corrected In TestPartner 5.4.0 and higher. As a result, Property or Content checks created for .NET DataGrid controls prior to TestPartner 5.4.0 may fail when executed in TestPartner 5.6.0. To work around this issue, either recapture these checks, or perform a "Save As Expected" on the failed check.
.NET Labels with a BackColor property set to Transparent that appear in a GroupBox control of a .NET application are captured incorrectly. TestPartner captures the text of the GroupBox control multiple times. This problem only occurs with .NET v1.0 and .NET v1.1.
Setting the value of a property of type Object generates an "Object Required" error message for variables declared as an Object of a specific data type by a referenced .NET assembly. To work around this issue, remove the referenced .NET assembly from the script and declare each variable which was previously defined by the reference to type Object.
When in IME composition mode, text may be recorded improperly. In addition, using the CaptureText() method while in IME Composition mode may cause an improper text capture. In either case, to workaround this issue, exit the IME composition mode prior to recording the next action, terminating a recording session, or using the CaptureText() method.
TestPartner scripts that record a switch between IME modes by selecting against the IME System Tray icon will not play back correctly if the current mode is not the same as the initial mode when the script was recorded. This is because the IME icon is actually a ToolBar button, which TestPartner identifies through its ToolTip. If the IME mode during playback is not the same as the recorded IME mode, the ToolTip is different, so the IME button can't be found when the script is played back. As with any script, the application under test should be restored to its original state before script playback. If the IME mode is restored to its original state, a script that records a switch between IME modes will playback correctly.
To avoid any possible issue while recording a switch between IME modes, use the IME hotkeys to record a switch between modes instead of selecting the mode using the IME system tray icon. TestPartner ignores the IME hotkeys and does not record them.
When recording type statements for Java applications in IME composition mode, changing the current control focus by clicking on a different edit control causes a temporary delay of up to 40 seconds during the recording process. To avoid the delay, exit the IME composition mode prior to clicking on a different control.
TestPartner may incorrectly compute a control's index while recording. This occurs rarely, but can cause the recorded script to be unable to attach to the control during script playback.
Various circumstances may cause TestPartner to incorrectly compute a control's index. One known instance of this is where TestPartner may incorrectly record the index of a Java control if the control has been previously recorded in the same script and the control's Z-order has been changed. For example, if a script records against a Java control that is in the foreground, then the control is moved to the back, subsequent recording against the control may record with a different index, and the script may not playback correctly. Similarly, TestPartner may not properly record the same index against a control after its Z-order changes.
If TestPartner incorrectly computes a control's index, work around the issue by returning the application under test to its state just prior to the action that is not playing back as expected, identifying the control, then adjusting the control's index in the recorded code with an appropriate value.
TestPartner allows command line execution of scripts using TP.exe. A command line execution issue was resolved that fixed the Auto-increment setting. This caused command line script execution from QADirector to always append script execution results to the log rather than to automatically increment the log. QADirector users and users who automate script execution through TP.exe can obtain information about a registry setting to disable the fix, providing backward compatibility with QADirector. The registry setting allows the Auto-increment logging value to be taken from the run environment rather than from the script execution command. Contact QACenter Customer Support for information about the registry setting.
An SAP limitation fails to update the Modified property, and TestPartner is not able to gather this information in any other way.
SAP eCATT stores TestPartner test data in the TP_EDIT or TP_EXEC database. If TestPartner is run within eCATT, and TP_EDIT or TP_EXEC have an old schema, TestPartner cannot start. Neither TestPartner nor eCATT can provide a detailed message why TestPartner cannot start. To resolve this issue, use the Database Maintenance Utility (DBMaint) to update the schema for both the TP_EDIT and TP_EXEC databases.
The SAP Document Object Model (DOM) does not provide a way to determine what part of an SAPTreeView control is clicked on when a click is recorded against the SAPTreeView. As a result, TestPartner cannot record a click that collapses any branch within an SAPTreeView control.
TestPartner does not support event creation and playback for SAP controls. TestPartner provides a high degree of synchronization with objects and controls in SAP applications, which greatly reduces the need for events used to synchronize with SAP applications. Error handling using the TestPartner TOnError object can be used to handle asynchronous type events. See the TestPartner help topic "Example Script - Error Handling" or the help topic "TOnError Object" in TestPartner's TPOSI Language Reference for details.
If you have uninstalled all previous versions of TestPartner but the installation process indicates that a previous version of the product is still installed, you may need to remove a registry key. In the Windows Registry Editor, delete the following registry key if it exists on your system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AF32ADB9-45B1-4736-A390-A0728138E1BB}
When installing TestPartner 5.6.0 on Chinese or Japanese operating systems, MDAC 2.7 displays an error message if a directory named using Chinese or Japanese characters is the leading directory off the root, for example C:\[Chinese Characters] or C:\[Chinese Characters]\[English Characters]. This issue does not occur when an English character named directory is the leading directory off the root. This is due to a limitation in the Install Shield program used to create the TestPartner installation, and does not impact your installation of TestPartner. Click OK to dismiss the error message and continue with the installation.
Compuware Customer Support can assist you with all your technical problems, from installation to troubleshooting.
Prior to contacting customer support, gather the following information:
800.538.7822
Refer to Compuware's FrontLine support web site for fast access to critical information about your QACenter product. You can read and print documentation, download product fixes, review frequently asked questions, or directly e-mail Compuware with questions or comments. The first time you access FrontLine, you are required to register and obtain a password.
Refer to Compuware's corporate web site at http://www.compuware.com for information about Compuware customer support policies and problem resolution process.
Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099
End of TestPartner Release Notes
(C) 2006 Compuware Corporation. All rights reserved. Unpublished rights
reserved under the Copyright Laws of the United States.