Release Notes

TestPartner 5.4.0

February 14, 2006


Obtaining the Latest Release Notes

System Requirements
What's New
Technical Notes
Known Issues
Contacting Compuware Customer Support

Obtaining the Latest Release Notes  back to top 

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.

System Requirements  back to top

TestPartner has the following minimum system requirements:

Input Method Editor (IME) Support

TestPartner supports the following IMEs for the listed input systems.

X - Supported

Japanese Input System



Windows 2000

Windows XP

Windows 2003




















Korean  Input System



Windows 2000

Windows XP

Windows  2003








IME 2000






IME 2002






Simplified Chinese Input System



Windows 2000

Windows XP

Windows  2003














MS-PinYin 3.0




































Enhanced Unicode





* Only appears with Windows XP and Windows Server 2003 with Office XP Multilingual Support complete install.


Traditional Chinese Input System



Windows 2000

Windows XP

Windows  2003


























New Phonetic






New ChangJie


















Big5 Code












What's New  back to top

Testing Using External Data Sources

TestPartner's ActiveData testing feature lets you leverage data in external files as input into scripts for powerful, comprehensive application testing solutions. ActiveData testing lets you perform multiple transactions against test applications using a different set of data for each transaction without writing complicated code or compromising existing data. ActiveData wizards guide you through the process of preparing scripts to use variable data from external sources. TestPartner also lets you write new data as required to existing data files without having to edit those data files manually.

Full Functional Testing Integration in Visual Studio Team System (VSTS)

TestPartner 5.4.0 integrates with Visual Studio 2005 Team Suite Edition as a fully integrated testing asset. Test any application within the VSTS environment using any TestPartner script from any TestPartner database or project as a VSTS functional test suite. You can add, edit, and execute TestPartner scripts from within VSTS, providing a fully integrated development and testing solution. View detailed test execution results and modify scripts based on test execution results within the integrated environment. You can also configure TestPartner script playback and database settings from VSTS.

To enable the functional testing integration, TestPartner requires the installation of certain VSTS components. See "Minimum VSTS Component Installation for TestPartner Functional Testing Integration" in the Technical Notes Section of the Release Notes for more information.

Importing and Exporting Test Assets

TestPartner's import and export utilities allow you to transfer test assets in XML format from one TestPartner database to another. Asset import and export simplifies project management and enables keyword testing. It also lets you share assets across a WAN, and utilize external version control systems. Use a wizard to quickly and easily import and export assets, or execute the import and export utilities from a command line for greater control over the import/export process. For either method, you can modify a number of parameters to customize import or export of test assets.

TestPartner Logs

TestPartner logs now include a summary view in HTML format which lets you quickly determine the run status of a script test run. Know at a glance if an overall script run was successful and the number of passed and failed checks. In addition, several new pre-defined filters let you quickly view the results of the latest cycle, its checks, and failed checks. Custom filters are expanded to include filtering by User Checks in addition to standard checks.

Support for Microsoft .NET Framework 2.0

TestPartner 5.4.0 includes full object recognition, capture, and playback support for the Microsoft .NET Framework 2.0. This includes the standard .NET Windows Forms controls shipped with the Microsoft Visual Studio 2005 development environment.

TestPartner supports the ability to recognize the HTML elements generated by an ASP .NET web page. TestPartner identifies these elements as HTML controls, and not as standard ASP .NET controls. ASP.NET controls included within the Web controls downloaded from Microsoft's web site are also supported. These controls include MultiPage, TabStrip, ToolBar, and TreeView.

.NET 2.0 Object Extension

TestPartner's use of VBA to extend object support using the Object() method includes .NET 2.0 objects. This feature allows TestPartner to interrogate .NET 2.0 objects in an application under test at runtime, which exposes properties, methods, and fields not available at design time. The .NET 2.0 object support includes the ability to display IntelliSense for the members of referenced .NET 2.0 objects. It also provides the ability to call methods and to get and set properties and fields of .NET 2.0 objects that are exposed at runtime. Due to VBA limitations, any .NET objects that use generics cannot be used with .Object for .NET.

Support for SAP 6.40 GUI for Windows

TestPartner 5.4.0 includes full object recognition, record, and playback support of SAPGUI 6.40 for Windows. This includes related SAP 6.40 GUI for Windows client controls and GUI elements. Object recognition and property retrieval is supported for standard SAP rendered controls and select mixed (4.6c ActiveX) controls as enumerated by the SAPGUI DOM. Support also includes version checking and check creation and playback functionality for relevant controls. TestPartner's synchronization with SAP applications virtually eliminates the need to create synchronous events in scripts that test SAP applications.

Note: Compuware recommends the use of SAPGUI 6.40 for Windows, patch 15 or later.

Support for Uniface 8.4.02

TestPartner 5.4.0 includes full object recognition, record, and playback support for Compuware Uniface 8.4.02. This includes all standard Uniface widgets. Object recognition and property retrieval is also supported for standard Uniface widgets. Support also includes version checking and check creation and playback functionality for relevant Uniface widgets.

Support for Sun Java 2 JDK 1.4.2, and 5.0

TestPartner 5.4.0 supports testing Sun JDK Release 1.4.2 and JDK 5.0. This includes object recognition, recording and playback of all currently supported AWT and JFC (Swing) controls, as well as new controls introduced in JDK 5.0. Script playback is forward and backward compatible, so any script recorded in JDK 1.4.1 or earlier can replay without alteration if properties of interest are not changed. TestPartner supports all previous packages under the specific JVM. TestPartner also tolerates the new Synth Look & Feel for Sun Java 5.0

TestPartner's extension matching support in Release 5.4.0 handles the dynamic nature of class names in JDK 1.4.2 and JDK 5.0. In addition, Java applications launched from the Java Web Start Manager or from a web page are also supported. Changes made to the Z-order of Java controls is not supported in this release. See the Known Issues section for more information.

Native Database Authentication

TestPartner 5.4.0 supports native database authentication for connecting to SQL Server and Oracle databases. When attempting to log on to one of these databases using a non-trusted logon name and password, TestPartner allows the native user name and password to be entered for database connection.

Note: Existing TestPartner users may need to configure their database connection. For more information see, Configuring a TestPartner Database Connection.

Enhanced HTML Table Support

TestPartner 5.4.0 provides improved automation and check support for symmetric or asymmetric HTML tables by enumerating through the table to access data in individual cells. TestPartner can obtain HTMLTable control details such as row and columns counts, individual cell values, and the ID of the top left table cell.

Technical Notes  back to top

This section includes technical information that may affect how you use the product.


Configuring a TestPartner Database Connection

TestPartner 5.4.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 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 TestPartner Logon dialog box or access "Configuring a TestPartner Database Connection" in the Installation and Configuration Guide or in TestPartner online help.

Notice of Improper TestPartner Database Manipulation

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.

TestPartner and Wide Area Networks (WANs)

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.

Notice of Database Support

Compuware is announcing that TestPartner 5.4.0 will be the last release to support Oracle 8.1.7 or MSDE 1.0 as a TestPartner database repository.


Additional Documentation for TestPartner Server Database Setup

The TestPartner Installation Guide contains detailed instructions on how to set up a database for TestPartner. However, there are additional instructions on creating new databases and updating database versions in the Getting Started section for Administrators in the TestPartner online help. You may also need to refer to these instructions depending on your database setup.


TestPartner and License Manager 4.0

TestPartner 5.4.0 ships with the Compuware License Administration Utility (LAU) 4.0, which uses License Manager 4.0. All TestPartner 5.4.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.


Minimum VSTS Component Installation for TestPartner Functional Testing Integration

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:

Visual Basic for Applications (VBA) Language Settings in TestPartner

During installation, users set the language to be used by TestPartner. Normally, VBA uses its own mechanism for deciding on the language it uses. If TestPartner and VBA languages are different, and TestPartner is localized to the selected VBA language, then TestPartner overrides VBA's mechanism and both TestPartner and VBA use TestPartner's language. However, if the language VBA uses is not a language TestPartner is localized to (such as Spanish), then VBA uses its mechanism to decide the language to use.

Installing TestPartner on a Computer With VBA 6.2 and Visual Studio .NET

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.

Record and Playback

Resetting IME Mode to Initial Recording State Before Playback

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.

Dismissing the Candidate Window When Recording Chinese Characters in a Single Line Edit Control

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.

Support for Four Byte Chinese Simplified Characters

TestPartner supports single-byte and double-byte encoded characters available through GB18030. TestPartner does not support four-byte encoded characters available through GB18030.

Record and Playback Facilities in TestPartner

When TestPartner is running concurrently with an application being tested, test record/playback facilities in TestPartner may be impacted by the following:

TestPartner recording or playback may slow down when testing applications on slower speed machines when several hundred controls exist on one page.

SAP Support

Setting Up TestPartner as the SAP eCATT External Testing Tool

SAP eCATT users who want to use TestPartner as the extended testing tool of choice for SAP Web Application Server 6.20 (patch 42 or later) or SAP Web Application Server 6.40 (patch 15 or later) must use eCATT to perform initial external tool setup. Please refer to SAP eCATT documentation for SAP Web Application Server at 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 and SAP Server Side Scripting Requirements

TestPartner requires server side scripting support to be turned on in SAP 6.20 GUI for Windows to identify, record, and playback SAP objects. SAP 6.20 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 To find the document, select the Advanced Search link and type "SAP GUI Scripting Security Settings".

SAP Communication Object and TestPartner

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.

Script Record and Playback Against SAP ITS 6.10 and 6.20 HTML Controls

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:

Default Property

Recommended Property


Src, Name




HTMLDIV (required in some cases)

ID or Parent ID


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.

Controls Support

Progress Bar Not Shown When Capturing a Property Check Against a JavaMenu Control

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.

Retrieving Cell Coordinates in a .NET DataGrid Control

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, 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.

Known Issues  back to top

This section describes known issues related to the current release of TestPartner.

TestPartner Test Assets

Object Map Availability in TestPartner

Object Map entries in TestPartner could be available in projects other than the Common project or the project to which they are saved.

Including Assets With the Same Name from Different TestPartner Projects

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.

Support for .NET Object Arrays When the Object's .NET Assembly is Referenced

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.


Oracle ODBC Driver Versions and

Using Oracle ODBC driver versions and 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 or earlier. This is an Oracle issue. Please contact Oracle for resolution details.

Record and Playback

Property and Content Checks Created Prior to 5.4.0 Against a .NET DataGrid May Fail

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 has been corrected In TestPartner 5.4.0. 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.4.0. To workaround this issue, either recapture these checks, or perform a "Save As Expected" on the failed check.

.NET Labels With Transparent Backgrounds Captured Incorrectly

.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 Error Message

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.

Text Recorded Improperly When in IME Composition Mode

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.

Recording a Switch Between Modes in an Input Method Editor (IME)

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.

Recording Type Statements for Java Applications in IME Composition Mode

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.

Incorrect Index Recorded Against Controls

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.

Logging Script Execution From a Command Line with QADirector

TestPartner allows command line execution of scripts using TP.exe with the COM interface. 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 the COM interface 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.

SAP Support

Modified Property Does Not Return Correct Value

An SAP limitation fails to update the Modified property, and TestPartner is not able to gather this information in any other way.

No Detailed Message Why TestPartner Cannot Start from SAP eCATT

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.

Recording the Collapse of an SAPTreeView Control in TestPartner

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.

Event Creation with SAP Controls

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 online Language Reference for details.


Previous Version of TestPartner is Detected

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}

Possible Error Message During TestPartner Installation to a Chinese or Japanese Operating System

When installing TestPartner 5.4.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 install TestPartner, and does not impact the installation of TestPartner. Click OK to dismiss the error message and continue with the installation.

Contacting Compuware Customer Support  back to top

Compuware Customer Support can assist you with all your technical problems, from installation to troubleshooting.

Before Contacting Customer Support

Prior to contacting customer support, gather the following information:



FrontLine Support Web Site

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.

Compuware Corporate Web Site

Refer to Compuware's corporate web site at 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.