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 installation media or from the program shortcuts on your desktop, you may not be reading the latest Release Notes. For the most recent version, 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 on to 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.
Your system configuration should meet the following requirements to successfully install and run TestPartner:
TestPartner supports the following IMEs for the listed input systems.
Legend
X - Supported
|
Japanese Input System |
Description |
File Name |
Windows 2000 |
Windows XP |
Windows 2003 Server |
Windows Vista |
|
|
MS-IME 2000 |
imejp.ime |
X |
|
|
|
|
|
MS-IME 2002 |
imejp81.ime |
|
X |
X |
|
|
|
MS-IME 2003 |
imejp9.ime |
|
X |
X |
|
| MS-IME (10.0.6000.0) |
N/A | X |
||||
|
|
||||||
|
Korean Input System |
Description |
File Name |
Windows 2000 |
Windows XP |
Windows 2003 Server |
Windows Vista |
|
|
IME 2000 |
imekr61.ime |
|
X |
X |
|
| MS-IME 2002 | imekr.ime |
X |
X |
|||
| MS-IME 2003 | imekr70.ime |
X |
X |
X |
||
| MS-IME (8.0.6000.0) |
N/A | X |
||||
|
|
||||||
|
Simplified Chinese Input System |
Description |
File Name |
Windows 2000 |
Windows XP |
Windows 2003 Server |
Windows Vista |
|
|
MS-PinYin 98 |
pintlgnt.ime |
X |
|
|
|
|
|
MS-PinYin
3.0 |
pintlgnt.ime |
|
X |
X |
|
| MS-IME 2003 | imsc40a.ime | X |
X |
X |
||
| MS-Pinyin IME (10.0.6000.0) |
N/A | X |
||||
|
|
||||||
|
Traditional Chinese Input System |
Description |
File Name |
Windows 2000 |
Windows XP |
Windows 2003 Server |
Windows Vista |
|
|
MS-New
Phonetic |
tintlgnt.ime |
X |
X |
X |
|
| MS-New Phonetic IME (10.0.6000.0) |
N/A | X |
||||
Note:
TestPartner provides full object recognition, recording, and playback support for applications running on Windows Vista (32-bit edition). Additionally, support is provided for new Vista controls such as the new task bar, customized column header drop-down control, and the command link button note property. Three new TestPartner objects and one property have been created to support these new controls:
TestPartner supports the recording and playback of applications with the User Account Control (UAC) option enabled in Windows Vista, however, the automation of the UAC dialog box itself is not supported. For more information, see Testing With the User Account Control (UAC) Option Enabled in Windows Vista. Additionally, see Recording and Playing Back Test Applications as an Administrator on Windows Vista for more information about Vista's new security settings.
The .NET Framework 3.0 is comprised of existing .NET Framework 2.0 components such as the Common Language Runtime (CLR) and Windows Forms. As a result, TestPartner supports Windows Forms applications run in conjunction with the .NET Framework 3.0.
TestPartner provides full object recognition, recording, and playback support for HTML-based Web applications running in the Mozilla Firefox Web browser. In addition to standard HTML elements, TestPartner supports FireFox user interface features such as the menu bar, toolbars, context menus, tabs, and the Options dialog box.
TestPartner supports the Java SE 6 major feature release. This includes support for object recognition, recording and playback of all currently supported AWT and JFC (Swing) controls, as well as support for new features and enhancements introduced in Java SE 6 such as the splash-screen API, table sorting and filtering, desktop APIs, and applications created using Java WebStart technology.
TestPartner includes full object recognition, recording, and playback support for SAP GUI for Windows 7.10 and SAP Web Application Server 6.40 and 7.00. This includes related SAP GUI for Windows 7.10 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 SAP GUI DOM. Support is also included for the SAP Business Explorer. For more information, see Recording Against Scroll Bars in the SAP Business Explorer.
The Visual Test Tutorial now includes the lesson "Playing Back Test Scripts From a Visual Test". In this lesson, you learn how to use test scripts and visual tests in conjunction with each other by creating a modular test in which a visual test plays back a test script, and then receives variable data from the test script that is used later in the visual test.
This section includes technical information that may affect how you use the product.
The access permissions of the folder in which the TestPartner database is installed are automatically applied to the TestPartner database. In a multi-user testing environment, you must ensure that required users have full access to the TestPartner database when installing the database in a location other than the default location.
When installing an Oracle client to use as a TestPartner database on Windows Vista, you must install Oracle client version 10gR2.3 and ODBC driver 10.2.0.3.0 or later.
When using an Oracle 9.2 client as a TestPartner database, TestPartner requires ODBC driver 9.2.0.8.0 or later
To use an existing TestPartner 5.4 or 5.6 SQL Server or MSDE database with TestPartner 6.1, you must create a new Data Source Name (DSN) using the SQL Server Native Client driver. This driver is automatically installed on your system by the TestPartner 6.1 installer. For more information on creating a DSN, refer to the "Creating a Data Source Name for a SQL Server Database" section of the TestPartner Installation Guide.
During the recording and playing back of a visual test, TestPartner captures and stores the screens and controls of the target application at each stage of the recording and playback. Because of the potential of capturing a large number of images and controls, you may experience a high growth rate of the size of your database. For more information, see the TestPartner Help topic "Limiting Database Growth".
To prevent SQL Server from inhibiting performance by requesting too much memory, Compuware recommends setting the maximum SQL Server memory to 25 percent of the total RAM of the system, unless the total RAM is 256 MB, in which case set the maximum server memory to 80 MB. This recommendation applies when using any version of SQL Server as a TestPartner database if SQL Server is running on the same machine as TestPartner.
For compatibility with QADirector, TestPartner enables TCP/IP when installing SQL Server 2005 Express. Be advised that enabling TCP/IP presents a security risk to outside attacks through the internet.
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 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.
The sample applications used in the TestPartner tutorials are designed and optimized to run on Internet Explorer 7. To ensure a user experience consistent with the lessons in the tutorials, Compuware does not recommend running the tutorial sample applications on the Mozilla Firefox browser.
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 Help. You may also need to refer to these instructions depending on your database setup.
TestPartner supports the recording and playback of applications with the User Account Control (UAC) security setting enabled provided the UAC dialog box does not appear during recording or playback. To disable the User Account Control (UAC) in Windows Vista:
In a multi-user testing environment, each TestPartner installation must be the same build as the other TestPartner installations. Failure to standardize the build may cause a TestPartner installation at a lower build to stop responding.
TestPartner ships with the Compuware License Administration Utility (LAU) 4.2, which uses License Manager 4.2. All TestPartner licenses can only be set and configured using License Manager 4.2. View the License tab of the QACenter installation media to install License Manager 4.2.
The license feature name for full TestPartner 6.1 functionality has changed from "955" to "TestPartner Developer". The new license feature name is not backwardly compatible with prior releases of TestPartner. If you plan to run TestPartner 6.1 with an earlier release of TestPartner, you will need to run a license server that contains licenses for both releases.
Windows Vista provides you with the option of running applications as a standard user or as an administrator. If you choose to run a test application as an administrator, you must also run TestPartner as an administrator. Conversely, if you run a test application as a standard user, you have the option of running TestPartner as either a standard user or an administrator.
A hot key or shortcut key refers to a keyboard key or key combination that invokes a particular command. For example, F11, CTRL+N or SHIFT+RIGHT ARROW. To reliably record hot keys in a text box control, you must exit standard recording mode and enter raw recording mode. For more information, see the TestPartner Help topic "Recording Hot Keys Using Raw Mode".
Microsoft has released a software update that changes the way in which Internet Explorer handles some Web pages that use ActiveX controls and Java applets. Once the update is installed, ActiveX controls from certain Web pages must be activated before they can be used. To enable an ActiveX control, a user must manually click the control.
As a result, TestPartner may record the activation of an ActiveX control that previously did not require activation. For example:
' Attach to Caption='SwingSet demo'
HTMLBrowser("Caption='SwingSet demo'").Attach
ActiveX("ClassName='Java Plug-in Control Window'").Activate
' Attach to JavaWindow
JavaWindow("JavaWindow", tpAttachChild).Attach
JavaButton("Index=4").Click
JavaComboBox("Index=1").Select "Philip, Lisa, Brent"
TestPartner has accommodated this change made by Microsoft in ActiveX behavior, and new test scripts recorded by TestPartner accurately record and play back the new ActiveX controls that require activation. However, existing scripts that interact with ActiveX controls that have changed may require re-recording.
There are techniques that Web developers can use to update their Web pages. Refer to Microsoft's MSDN Web site for more information about these techniques.
By default, the TestPartner General option Minimize on Playback is set to Yes. When this option is set to Yes, TestPartner minimizes to the taskbar each time you step through a line of code in a test script or a step in a visual test while in Debug mode. To change the default Debug mode playback behavior, set Minimize on Playback to No. When this option is set to No, TestPartner minimizes only when you step through a line of code in a test script or step in a visual test that performs an action against the target application. For example, clicking a button or typing in an edit box.
When TestPartner is running concurrently with an application being tested, test record and 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.
TestPartner supports SAP GUI for Windows 6.20 (patch level 42 or later) and SAP GUI for Windows 6.40 (patch level 15 or later) and SAP GUI for Windows 7.10 (patch level 2 or later).
To configure SAP GUI for Windows, SAP GUI for HTML, and SAP eCATT for use with TestPartner, perform the following steps:
Note: For more information about these configuration steps, refer to the SAP Help Portal (http://help.sap.com) and search the SAP R/3 and R/3 Enterprise documentation for the SAP Help topics listed after each step.
To more reliably identify SAP Window objects, TestPartner adds the Caption property as a property of interest in the default recording profile and removes the SAPID property as a property of interest from the profile.
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 play back 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.
Test scripts recorded against HTML controls in SAP ITS 6.10 and SAP ITS 6.20 may not play back properly. This is because the default properties used to record against HTML controls contain additional elements that cause indexing to be different upon subsequent test 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 SAP ITS 6.10 and 6.20 HTML controls 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.
In TestPartner 6.1, an additional result run status type, Playback Error has been added to distinguish playback errors from checks and verifications that fail. Examples of playback errors include:
A result is assigned a Failed run status when a check or verification is run and the criteria defined by the check or verification logic is not met. For example, TestPartner assigns a Failed run status to a visual test that runs a text check that does not verify the expected text in the test application.
Prior to TestPartner 6.1, results were assigned a Failed run status whenever the test contained either playback errors or failed checks or verifications. Consequently, to handle the differences between 6.1 results and results created prior to 6.1, TestPartner will retain the original run status of a result when you import the result into 6.1. The run status will not change to fit the 6.1 criteria for assigning a run status. For example, a TestPartner 6.0 result with a run status of Failed imported into TestPartner 6.1 will always display a Failed run status even if the same result in 6.1 would be assigned a Playback Error.
The availability of Object Map entries is not limited to the Common project and the project in which they are saved. Object Map entries are available in any TestPartner project. For more information about Object Map project rules, see the TestPartner Help topic "Modifying Record Attach Name Options".
TestPartner supports the playback of test scripts from Visual Studio Team Suite SP1 either as a standalone asset or as a part of a Visual Studio test suite. Playback of visual tests from Visual Studio Team Suite SP1 is not supported.
This section describes known issues related to the current release of TestPartner.
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.
Note: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
In the following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{TestPartner version-specific key}
Delete the registry key for the version of TestPartner you have installed:
• TestPartner 5.2.1 {AF32ADB9-45B1-4736-A390-A0728138E1bb}
• TestPartner 5.3.0 {32E99FAB-30A3-43BD-95AA-D16C31B0D2DB}
• TestPartner 5.4.0 {32E99FAB-30A3-43BD-95AA-D16C31B0D2DB}
• TestPartner 5.6.0 {679B70D8-D304-414E-9CED-DB67B106B4AF}
• TestPartner 6.0.0 {8C3E03F6-EB13-40F2-827E-BF971DD70909}
• TestPartner 6.1.0 {AB5F5371-C53E-47D7-925A-FA792350EF5A}
TestPartner does not function when a remote desktop or RDC is minimized. When you connect through the RDP to a desktop, you take ownership of the desktop by attaching to the desktop with your mouse and keyboard. If the desktop is minimized without ownership of the desktop being released, any playback of mouse clicks or keystrokes is undefined. The recommended configuration is to run TestPartner on a VMWare-server and connect through VMWare-client software. This allows replay to continue even if the client has been closed.
TestPartner may incorrectly compute a control's index while recording. This occurs rarely, but can cause the recorded test script to be unable to attach to the control during 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 test script and the control's Z-order has been changed. For example, if a test 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 test 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 and no other unique identifiers exist, 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 does not record the scrolling movement of the SAP Business Explorer scroll bar. To work around this issue, use the scroll bar to position the desired item so that it is visible. Next, click above or below the scroll bar to record a click position that will mark the position of the item. Make sure that after clicking above or below the scroll bar, the item remains in view. During playback, TestPartner will use this click position to bring the item into view.
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 has 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 Test Script - Error Handling" or the Help topic "TOnError Object" in the TestPartner Help for details.
If two TestPartner assets with the same name belong to different TestPartner projects, using the $TPInclude statement or the Include() method in the same test script can cause a VBA error. The error occurs when attempting to open both assets. When this happens, TestPartner displays 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 test 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.
Compuware Customer Support can assist you with all of 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) 2007 Compuware Corporation. All rights reserved. Unpublished rights
reserved under the Copyright Laws of the United States.