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 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.
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's new visual test asset complements VBA-based test scripts as the main testing asset. Record and edit tests against target applications without generating a programming language based script. Tests now display as a series of steps in clear, non-technical language. Non-technical testers now have the ability to quickly create powerful, reliable, and comprehensive testing solutions. This significantly reduces the total cost of ownership and allows users familiar with the business processes being automated to take greater ownership in the testing process.
Controlling data captured and saved during test recording and updating recorded tests is easier than ever. Visually set actions and values against controls in target applications at the test step level. Add plain-text descriptions for test steps to communicate additional test information to test team members.
You can still leverage your VBA-based test script and continue to execute test scripts created in previous TestPartner releases.
TestPartner has significantly enhanced its interface for the 6.0 release. TestPartner's Visual Navigator is an action-based interface that lets you see the relationship between a text based action step in a test and the object of the action. The interface allows non-technical users to quickly select actions to perform against controls, and grasp how underlying control properties affect how or what to automate.
The interface allows more guidance throughout the entire test process. View application windows being automated in TestPartner's new Visual Navigator and make testing changes without accessing the target application. View and update the critical properties of an action in the same window as the textual description for the action. Use the thumbnail images in the Visual Navigator's Storyboard to quickly determine a test's flow and points at which it interacts with the target application.
TestPartner's Start Screen provides guidance to let you begin creating and collaborating on testing solutions in TestPartner. Common tasks are now a click away, letting you be more productive on a daily basis. User assistance for the most common tasks is immediately available in the Help pane, as well as instant access to the TestPartner Visual Test Tutorial and support through Compuware's Frontline web site. Begin recording tests immediately after starting TestPartner without any pre-recording setup, and access your most recently created visual tests displayed in the Visual tests pane.
To help you analyze all aspects of each test run, TestPartner's new results interface includes the Visual Navigator, which graphically represents the elements of each test run and allows you to interact with each element. In the Screen Preview pane, you can see any differences between screens captured during the initial recording of a visual test and the screens captured during playback of the visual test. If differences exist, you can update the visual test with the screens captured during playback right from the Screen Preview.
The results interface organizes result information using tabs that provide quick access to a summary report of the playback, any passed or failed checks or verifications, flagged steps, and the detailed result of every step in a visual test or line of code in a test script.
To document your testing procedures or collaborate with other testers, you can print results, save results to a file, or flag items to remind yourself or others about an important issue in a result. You can also create and apply filters to display only the result information that is of most interest.
With TestPartner, any tester can discover structural or execution issues with production tests to ensure that they continually perform as expected, thereby freeing up development resources that were needed to diagnose test execution issues. Non-technical testers can now visually set up, manage, and step through test execution, as well as see values returned from any type of variable including ActiveData.
Reduce the overall maintenance costs of your testing efforts by using variables in visual tests. Variables can be used for any values used in testing letting you increase reliability while reducing dependence on hard test data. Variables used in a visual test and variables used to define the test playback environment are visually managed as step properties for easy access. You can also leverage existing data sources and perform powerful transaction-based testing with ActiveData variables. ActiveData testing lets you perform multiple transactions against test applications using a different set of data for each transaction without compromising existing data.
Flag items in a visual test to remind yourself or others to follow up on important issues. Flagging an item inserts a flag icon that when clicked displays a description and other information about the flag. Assigned flags appear on the Start Screen of the assigned tester and when clicked open the visual test containing the flagged item.
Document test cases by printing the steps and screens of a visual test using TestPartner's enhanced printing capability. Customize the output by choosing to include a summary page, associated screens, flagged steps, or properties of each step. Use the Print Preview feature to verify how the print output will look before it is printed. For test scripts, print the entire test script or only a selected portion.
TestPartner's ActiveData feature is extended to visual tests. Leverage existing data in external files as data input into visual tests for powerful, comprehensive application testing solutions. Use ActiveData with repetition logic in visual tests to perform multiple transactions against test applications. With ActiveData, you can use a different set of data for each transaction without writing complicated code or compromising existing data. When using ActiveData in visual tests, you can also write new data as required to existing ActiveData files without having to edit those data files manually.
TestPartner supports testing of .NET applications that run in multiple application domains. This includes object recognition, along with the recording and playback of controls in any application domain of .NET applications. Use the AppDomain property in visual tests, test scripts, and property checks to return the name of the application domain in which a specified .NET control is running.
TestPartner installs SQL Server 2005 Express SP2 as the default database. To use SQL Server 2005 Express, TestPartner requires MDAC 2.8 (2.80.1022.3), .NET Framework 2.0, Windows Installer 3.1, and either Windows Server 2003 SP1, Windows XP Professional SP2, or Windows 2000 SP4. The TestPartner installer automatically installs the required MDAC, .NET Framework, and Windows Installer version if they are not already currently installed.
When using a SQL Server 2005 Express database, database records from existing databases must be copied into the new SQL Server 2005 Express database. For more information, see the TestPartner Help topic "Copying Records from one Database to Another".
Each computer using SQL Server 2005 Express in a multi-user environment must be enabled for remote connectivity. To enable SQL Server 2005 Express for remote connectivity, refer to the Microsoft support article "How to configure SQL Server 2005 to allow remote connections".
TestPartner can also install Microsoft Access 2000 as the TestPartner database. To install Access 2000, clear the SQL Server 2005 Express check box in the Select Features page of the TestPartner Installation wizard.
Use the Test Logic Designer wizard and Logic Toolbox to quickly and easily enhance the power and flexibility of a visual test by including test logic that expands the basic capability of a recorded visual test. The Test Logic Designer wizard helps you define a condition from which to base an action, such as running a sequence of test steps or sending a pass or fail message to the test results. The Logic Toolbox is a navigational aide that helps you choose the right type of test logic for your specific needs to insert into a visual test.
TestPartner provides new objects, methods, and properties to perform a range of commonly used numeric and string based functions, as well as access system information. Expose these utility methods and properties by using the following objects in TestPartner test scripts:
Use the BitmapExists() and TextExists() methods in a test script to verify the existence of a bitmap image or text string when the specified bitmap or text is not found. Search for multiple instances of a bitmap or text by specifying an area of the target application in which to verify the existence of the bitmap or text.
In TestPartner, administrative rights are not required to change a logon password. Any TestPartner user with access to a database can change their password. Click Tools>Change Password to change your TestPartner logon password.
TestPartner supports the recording and playback of the following terminal emulation software:
For more information about testing terminal emulator-based applications, see the TestPartner Help topic "Testing Terminal Emulator-based Applications Using Raw Mode".
TestPartner provides support for integrating with QADirector, Compuware's test management solution that helps you manage a centralized library of test scripts, including manual tests, automated test scripts, test data and user-defined or custom tests.
From QADirector, you can create a TestPartner visual test or test script, and then play it back and analyze the results. Additionally, you can edit existing visual tests or test scripts.
TestPartner includes object recognition, record, and playback support for Compuware Uniface 9.1.01. This includes all standard and new Uniface widgets. Object recognition and property retrieval is also supported for standard and new Uniface widgets. Support also includes version checking, along with check creation and playback functionality for relevant Uniface widgets.
TestPartner can run in VMWare Workstation 5.5, Player 1.0, Server 1.0, and ESX/GSX Servers 3 provided the following requirements are met:
TestPartner supports license borrowing which allows you to borrow and return available TestPartner licenses from the License Administration Utility. To enable license borrowing, you must request an updated license through your normal support or sales channel. For more information about managing borrowed licenses, refer to the "License Borrowing" section of the DLM Licensing Guide.
This section includes technical information that may affect how you use the product.
To use an existing TestPartner 5.4 or 5.6 SQL Server or MSDE database with TestPartner 6.0, 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.0 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".
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.
When using an Oracle 9i Client as a TestPartner database, Compuware requires Oracle ODBC driver 9.2.0.8.0 or later.
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.
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.
Compuware is announcing that TestPartner 6.0 will be the last release to support Internet Explorer 5.5, MSDE 2.0, Oracle 9.0.1, SQL Server 2000 SP3a, and Sun and Java JDK and JVM 1.2.x, including Swing and AWT.
TestPartner ships with the Compuware License Administration Utility (LAU) 4.1, which uses License Manager 4.1. All TestPartner licenses can only be set and configured using License Manager 4.1. View the License tab of the QACenter installation media to install License Manager 4.1.
TestPartner 6.0 is the last release to use the license feature name 955 to enable full TestPartner functionality. In future TestPartner releases, the license feature name that enables full TestPartner functionality will change from 955 to TestPartner_Developer.
Future TestPartner release licenses will not be backward compatible with earlier releases of TestPartner. If you are planning to run TestPartner 6.0 or earlier concurrent with a release later than TestPartner 6.0, you will need to run a license server that contains licenses for both releases. Additional information will be provided in the Release Notes of the next TestPartner release.
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). Users upgrading from SAP GUI for Windows 6.20 to SAP GUI for Windows 6.40 may experience performance degradation. When upgrading to SAP GUI for Windows 6.40, make sure to use patch level 15 or later. The performance issue is currently being investigated.
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 play back 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 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.
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.
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.
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}
Due to a software limitation, the TestPartner 5.6 installer does not prevent you from installing TestPartner 5.6 on a computer that already has TestPartner 6.0 installed. If both are installed concurrently, you must uninstall both versions and then reinstall the desired version.
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 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.
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 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 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.