Release Notes

TestPartner 05.03

January 10, 2005

 

 

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:

For English:

For Japanese:

For Korean, Simplified Chinese, and Traditional Chinese:

Microsoft Windows XP Professional with Service Pack 1a and Service Pack 2, Windows 2000 with Service Pack 4, or Windows Server 2003 (formerly named .NET server 2003) including Standard Edition (32 bit) and Enterprise Edition (32 bit).

For all Languages:

Input Method Editor (IME) Support

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
IME 2002 imekr.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:


What's New  back to top

TestPartner Internationalization and Localization

TestPartner 05.03 is a Unicode application that runs on supported Microsoft operating systems for Japanese, Korean, Traditional Chinese, and Simplified Chinese. In addition, the TestPartner 05.03 user interface and end user documentation is translated for Japanese. TestPartner supports all object recording and playback of supported objects on these platforms and in Unicode applications. TestPartner's user interface is updated in the 05.03 release to support international settings for numbers, dates, and times.

To allow TestPartner to record and playback against applications with Unicode characters that may not be recognized by the testing computer's active code page, TestPartner 05.03 has added a new test asset type. A String Map asset allows a logical name (an alias) to be associated with a string that may contain unrecognizable characters. String map assets also eliminate a test scriptís dependence on raw strings which may change if the target application is modified.

Text Capture Support for GDI+ or Glyphs

TestPartner 05.03 supports text capture for applications that implement GDI+ or glyphs, including applications written in .NET that display their text using GDI+. Glyphs are used by Windows when East Asian fonts are installed (Windows XP) or when fonts for a complex script are installed (Windows 2000 English or Windows XP). GDI+ and glyph support resolves the issue of captured text using the CaptureText() method appearing garbled in text checks, field checks, and screen events.

.NET Object Extension

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

Support for SAP 6.20 GUI for Windows

TestPartner 05.03 includes full object recognition, record, and playback support for patch 42 of SAPGUI 6.20 for Windows. This includes related SAP 6.20 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.

Support for Unicode SAP eCATT Databases

TestPartner 05.03 is capable of interacting with and saving data to either an ANSI or Unicode SAP eCATT backend. This increased flexibility allows TestPartner to communicate with a Unicode backend which is capable of storing and displaying Unicode data.

Enhanced TestPartner Execution Bridge

In addition to TestPartner's QARun execution bridge, TestPartner 05.03 can execute scripts created in WinRunner 7.5. This allows current WinRunner customers to reuse their established test asset base in TestPartner. Specify an existing WinRunner script name from any TestPartner script, and WinRunner launches and runs the script when the TestPartner script executes. When the WinRunner script completes, TestPartner shows the relative success of the script execution and allows users to select a line in the script to view its execution details in the named execution log.

"Save All as Expected" Check Option

TestPartner now provides a Browsing Log view option for new versions of all failed checks to be created with the actual results of the checks saved as the expected result.

"Manage Attach Name Profile" Dialog

The Manage Attach Name Profile dialog is now accessible directly from the Tools menu. Click Tools>Manage Attach Name Profile to display the dialog.

Support for Microsoft .NET Framework 1.1

TestPartner 05.03 includes full object recognition, capture, and playback support for the Microsoft .NET Framework 1.1. This includes all related .NET Windows Forms controls shipped with the Microsoft Visual Studio .NET development environment.

As part of this enhancement, TestPartner also fully supports Internet Explorer 6.0 testing on the XP Professional platform. TestPartner also supports the ability to recognize the HTML elements, called .NET WebForm controls, created by the web services within certain browser types on the client. ASP.NET controls included within the Web controls download from Microsoft's web site are also supported. These controls included MultiPage, TabStrip, ToolBar, and TreeView

Support for JDK 1.4.0, 1.4.1, and Java Event Model 1.0

TestPartner 05.03 fully supports testing Sun JDK Release 1.4.0 and 1.4.1. This includes object recognition, capture and replay of all currently supported AWT and JFC (Swing) controls, as well as new controls introduced in Java 1.4.1. Script playback is forward and backward compatible, so any script recorded in JDK 1.3 or earlier can replay without alteration if properties of interest are not changed. TestPartner supports all previous packages under the specific JVM.

TestPartner's extension matching support in Release 05.02 handles the dynamic nature of class names in Java 1.4.1. In addition, Java applications launched from the Java Web Start Manager or from a web page are also supported.

To accommodate older applications, support for Java Event Model 1.0 is added to TestPartner Release 05.03. This allows identification and management of controls that use deprecated Java event handling support.

Support for Microsoft XP Professional

TestPartner 05.03 runs as a 32-bit application on Windows XP Professional Service Pack 1a and Service Pack 2, and supports new XP professional controls, including the new task bar, start menu, and themes. It also provides full support for Microsoft XP Professional common controls, and controls in XP Professional compatible applications. Full support includes object recognition, capture, and playback. Properties and checks are fully supported in Microsoft XP Professional. As part of this enhancement, TestPartner also fully supports application testing in Java and Internet Explorer 6.0.

Support for Multi-user Databases

TestPartner's database now allows multiple users to execute, edit, and save test assets. A read-only facility provides version support to prevent users from being able to check out and overwrite the same script. TestPartner 05.03 supports multiple users on the following databases:

TestPartner also supports Microsoft Access 2000 as a single-user database only.


Technical Notes  back to top

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

Databases

Multiple Database Users and TestPartner

Because MSDEís performance is a function of server load, not number of users, Compuware recommends MSDE only be used when there are five or fewer users on the database. Use another supported user database for more than five users.

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.

Documentation

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 Database Maintenance Utility chapter of the TestPartner Getting Started Guide. You may also need to refer to these instructions depending on your database setup.

Microsoft HTML Help Control in TPOSI Help Topics

Some topic link functionality in HTML help is provided by a Microsoft ActiveX HTML Help control. TestPartner uses this HTML Help control in its online Language Reference (TPOSI Help). Some of Microsoft's security patches have changed the control and caused the links in the controls to be unavailable or no longer work. On Windows 2000 Service Pack 4, links may appear as a small box with a dot in the center. Installing the Microsoft June 2003 cumulative patch for Internet Explorer and the Critical Update 811630 address this issue. For more information about this issue, visit the Microsoft Support Web site at http://support.microsoft.com and search for Knowledge Base articles 818529 and 811630. To download and install the updates, visit http://windowsupdate.microsoft.com.

Environment

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.

TestPartner and Supported Windows Spanish Operating Systems

TestPartner only supports Windows Spanish Operating Systems when VBA 6.2 (6.0.8714) is installed. TestPartner does not support Windows Spanish Operating Systems if any other version of VBA is installed. TestPartner installs VBA 6.2 (6.0.8714).

TestPartner and DevPartner Studio

Users wishing to launch a Compuware DevPartner Studio (DPS) code analysis tool application from a TestPartner script can do so using the VBA Shell function. For more information on using this function, refer to the Visual Basic Language Reference in Microsoft Visual Basic help, which is available from the TestPartner Help menu.

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.

Running TestPartner With McAfee Virus Scan

Users of McAfee's Virus Scan products may experience performance degradation while starting TestPartner when Virus Scan is also loaded. However, this performance degradation does not impact TestPartner while it is running.

Record and Playback

Break on Unhandled Errors Setting for Visual Basic Options in TestPartner

To allow TestPartner to handle and display VBA runtime errors during script execution, the VBA Break on Unhandled Errors setting in the Visual Basic Options inside TestPartner is disabled. This setting is in the General tab of the Visual Basic options, which is accessed by clicking Tools>Visual Basic Options.... This setting is only disabled for VBA when using TestPartner.

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.

Windows Start Button Playback

When the pressing of the Windows Start button is played back in a script, it will take a few seconds for the action to occur. This is because the context of the menu is SystemTray, which is part of the Windows shell. Script synchronization must wait for the Windows shell to become available. Availability depends on how heavily the computer is bound to the network and the DNS speed of the computer playing back the script.

Another reason for the delay is that the menu does not have a selected item when it pops up. The time for script synchronization to recognize that an item is selected, and the time to artificially select the first item and start actual playback can contribute to the delay.

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.

Changing the State of Property Checks Prior to Execution

Once a property check is captured against a control, do not change the state of the control that the property check was captured against. Changing the state can cause the check to fail verification. Some controls (normally ActiveX) also contain properties which change state during the property check capture, based on whether message response or overriding of properties has occurred. Use the 'Save as Expected' functionality to change the expected results for the property check to the recorded results. Use the exclude functionality to exclude properties from check verification.

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 must use eCATT to perform initial external tool setup. Please refer to SAP eCATT documentation for SAP Web Application Server 6.20 at http://help.sap.com. Open the Web Application Server 6.20 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 https://websmp206.sap-ag.de/support. 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.

Verifying a Property Check Against an SAPWebViewer2D Control.

Property checks verified in TestPartner against the SAPWebViewer2D control may fail even if no changes have been made to the captured control or the target control. An initialization issue with SAP can cause differences to exist within the ActiveX.LayerName property, whose items will contain an array that appears as garbled text. This issue occurs only when an image is not selected for the captured control.

To work around this issue, make sure an image is selected for the control before capturing, or perform a "Save as Expected" command against the failed check if the SAPWebViewer2D control has been captured without the image selected.

Inaccurate Differences For Failed SAPALVGridView Control Property Checks

If a property check created against an SAPALVGridView control is verified, and then a different cell in the control is clicked and the check is reverified, the check fails as expected because the control has a focus change. However, the check difference results may be incorrectly reported.

This happens because SAP can sometimes return a space at the end of cell text. For example, a cell that returned "123" in the initial check verification may return "123 " when the focus changed. As a result, a large number of differences can be reported against the Items property of the SAPALVGridView control. This does not interfere with the proper evaluation of the check itself, and the check still passes or fails correctly.

Recording a Click Against a Button Inside of an SAPALVGridView Control.

Clicking on a cell within an SAPALVGridView control can display an icon within the right side of the cell. Clicking the icon accesses a list of available values for the cell in a separate application window. When recording this sequence, TestPartner records the clicks in the cell using the SelectIndex() method, similar to the following sample:

SAPWindow("Application=SAPLOGON.EXE SAPID='/app/con[0]/ses[0]/wnd[0]'").Attach
        SAPALVGridView("Name=shell").SelectIndex 12, 5
        SAPALVGridView("Name=shell").SelectIndex 12, 5

This recorded code may fail to playback properly because the SAP scripting API does not expose a method that TestPartner can use to determine what part of the cell was clicked. As a result, the recorded code cannot determine if the icon within the cell was clicked.

To work around this issue, record the sequence in raw record mode, which records clicks within the cell that playback properly. Recording the sequence in raw record mode produces code similar to the following:

    SAPWindow("Application=SAPLOGON.EXE SAPID='/app/con[0]/ses[0]/wnd[0]'").Attach
   SAPALVGridView("Name=shell").Attach
       SAPALVGridView.Click 409, 238
       SAPALVGridView.Click 409, 238

Controls Support

Capturing Data in ComboBox Controls

ComboBox controls can be populated either when its program initializes, or only once an input event such as a mouse or keyboard input, or an event message has been received by it. If a ComboBox control is populated only when an input event is received by it, TestPartner will not be able to capture data from the control until after the input event is received by the control. One example of this type of ComboBox control is the Address ComboBox in Internet Explorer.

The best way to determine if a ComboBox control is populated only after an input event is received by it is to capture it in a content check. If there is data contained in the ComboBox control, but the Details tab of the content check does not show any items captured, then the control is populated only when an input event is received by it. Once you click the ComboBox control's drop-down arrow to display the items in the control, TestPartner will then be able to capture the control's data.

Updating Scripts that Capture Text in Applications that Implement GDI+ or Glyphs

TestPartner supports text capture for applications that implement GDI+, including applications written in .NET that display their text using GDI+. As a result, any scripts created in previous releases of TestPartner that use the CaptureText() or TextSelect() commands against .NET or GDI+ applications or glyphs may no longer work, since the text in these applications is now being retrieved properly. Checks and events that use the CaptureText() or TextSelect() commands in these scripts may have to be recreated in order for them to work properly.

Manipulating Navision AssistEdit Controls Within Navision TableBox or TextBox Controls

Navision applications can have AssistEdit controls within a TableBox or TextBox control. When recording, in order to manipulate an AssistEdit control within a TableBox or TextBox, you must first click to select the table cell or text box with the AssistEdit control. After manipulating the control you must also click to select the table cell that contains the control. This will ensure proper script playback. For a Navision TableBox control, the recorded script would be similar to the following:

NAVForm("NAVForm", tpAttachChild).Attach
NAVTableBox("Caption=Control1").Select 14, "", "DropDown"
NAVTableBox.SetCellText "Sale"
NAVTableBox("Caption=Control1").Select 14, "Sale", "None"

When it occurs within a Navision TableBox control, the Assist Edit control may not be referenced in the code. In this recorded script, the manipulation of the AssistEdit is done with the Select method and the AssistType parameter (Set to DropDown in the second line and "None" in the fourth line) which is unique to the Select method used for Navision TableBox and TextBox controls.


Known Issues  back to top

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

TestPartner Test Assets

TestPartner Alias Mapping and New Control Support

With new releases of TestPartner, support for new controls is often implemented as well as enhanced support for existing controls. An alias map entry contains the name of a control's class. If added or enhanced control support causes an aliased control to be recognized by a different class name, its existing alias map entry with the old class name will no longer be valid. This could potentially cause existing scripts with an affected alias map entry to not playback properly. To allow the alias map entry to work again, edit the entry to contain the control's class name as it appears in the current TestPartner release. This can be determined by using the "Identify" function on the control.

Default Cursor Placement in New TestPartner Scripts

When creating a new script in the Visual Navigator, the cursor may not always be placed at the default cursor placement set in the Options (set with the <CR> tag). This is because the Visual Navigator does not represent every line in the script. As a result, default cursor placement may not always be at the <CR> tag. If this happens, change the cursor placement in a script by switching to VBA Code view and manually placing the cursor at the desired location.

Maximum Script Size in TestPartner

Due to a limitation of the Microsoft VBA editor, a single TestPartner script cannot exceed 65,000 lines of code. If this limit is exceeded during recording, TestPartner stops recording without notification. If this limit is exceeded and discovered during compilation of the script, TestPartner displays an "Out of Memory" message from VBA. As a workaround, consider using a driver script, or dividing a long script into multiple scripts and using the Run command to call each script. See TestPartner's online help for information about driver scripts. See TestPartner's online Language Reference for information about the Run command.

TestPartner Scripts and the Visual Basic Variable Declaration Option

Certain Visual Basic options can be set in TestPartner, including an option to require variable declarations in scripts. Selecting this option adds the Option Explicit statement to general declarations in any new script. If a script is created with this option turned off, then the option is turned on and that script is opened, the Option Explicit statement will be inserted into that script. If variables were not pre-declared, then the script will not compile. This problem may occur in a shared database environment if one user has this option on, while another has it off. Work around this issue by ensuring all users in a shared database either have this option enabled or disabled.

Naming TestPartner Scripts Using Object Names

If a TestPartner script is assigned the same name as a TestPartner object, and that object is used in the script, its methods and properties will not be exposed. TestPartner will only expose the VBA methods and objects available to the script, which typically are the VBA Main method and the Name Property. For example, if a script is named TCheckBox, and the TCheckBox object is used in the script, IntelliSense will only show the Main method and the Name property, rather than all the methods and properties for TCheckBox. To avoid this problem, do not name TestPartner scripts the same name as any TPOSI or VBA object.

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't be left as what VBA changed it to because that could break scripts in the case of 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.

Check Names With Invalid Characters

TestPartner validates the names of checks for the following invalid characters:

\ / " : * ? | = . '

Checks created in previous releases of TestPartner execute correctly within existing scripts, changes made to the checks cannot be saved. Compuware recommends that these checks are renamed and all script references to these checks modified accordingly. When a check is renamed, the new name is validated by TestPartner to ensure that it does not contain invalid characters.

To modify the scripts that use checks with invalid names:

  1. Start TestPartner and display the Asset Browser by choosing Asset Browser from the View menu.
  2. In the Asset Browser, select the View button and ensure that the projects that contain invalid check names are selected as visible.
  3. Select Check from the Asset Types list. The list of checks displays.
  4. Select the first check that contains one of the invalid characters from the list.
  5. Choose Includes from the View menu. The Include Info window displays.
  6. Click the Included By tab. The scripts that use the selected check display.
  7. Double click on a script name to open it in TestPartner.
  8. Choose Find from the Edit menu to search for the check name. The Find dialog box displays.
  9. Enter the invalid check name in the Find What field. Use the Find dialog box to find each occurrence of the invalid check name and replace them with a check name that does not contain invalid characters.
  10. Repeat steps 6 through 9 for every script that displays in the Include Info window.
  11. Once all occurrences of the invalid check name have been replaced in the included scripts, rename the original check. To do this, select it in the Asset Browser, then select Rename from the File menu. Rename the check with the name used when replacing the invalid check name in the scripts.
  12. Repeat the process until all invalid check names in the Asset Browser check list have been changed.

Saving User Forms in TestPartner

If a user form created and saved, the "Save As" feature will be disabled. To work around this, save the user form using the File>Save command, which saves the user form with a default name, then select the form in TestPartner's Asset Browser and choose File>Rename. The desired name for the form can then be entered in the Rename Asset dialog.

Saving Test Data Using the Data Test Wizard

If a new script is created and populated using the Test Data Wizard, and then saved with a unique name, the script will fail and the test data information will be lost. To work around this issue, first create a new script and immediately save it with a unique name. Then populate the script using the Test Data Wizard and the script will run and the test data information will be saved.

Locating an Image Map Asset that Includes an SAPTreeView Control

If an Image Map asset includes an SAPTreeView control within its captured area, using the Locate function to locate the mapped area may produce a message that TestPartner is unable to locate the object. Synchronization between TestPartner and SAP does not allow any focus to be removed from the object before capturing any of its area in an Image Map. To work around this issue, make sure that all focus is removed from the SAPTreeView control and no items are highlighted in the control before capturing any of its area for an Image Map asset.

.NET References and Shared Modules

.NET references cannot be created in shared modules. If a .NET reference is added to a shared module, it will stay added to the shared module, but the corresponding COM reference is lost. To work around this issue, add the required .NET reference to a module, then include that module in other assets that require the .NET reference. The statement to include the module containing the .NET reference can also be added to the TestPartner default script template, which will automatically include the module and its .NET reference to any new VBA asset created.

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 a GPF.

Databases

Unlocking TestPartner Databases in the Database Maintenance Facility

If a TestPartner database is opened in the Database Maintenance Facility (DBMaint), then another database is opened without first closing DBMaint, the first database opened remains locked even though DBMaint has closed its connection to it. If an attempt to access that database is then made in TestPartner without first closing DBMaint, the database lock prevents TestPartner from accessing that database.

To work around this issue, close the database by closing DBMaint itself before attempting to open another database in DBMaint. This will unlock the database so it can be used by TestPartner. This issue does not apply if the first database opened is a Microsoft Access database.

Environment

Installing TestPartner on a Computer with Office XP and the Office XP Developer Add-in

If TestPartner is installed on a computer with the Office XP developer add-in installed, TestPartner may not initially work properly. When attempting to log in, TestPartner will display two messages stating that the Visual SourceSafe client is not installed. Click OK to reply to these messages, but once in TestPartner no new assets or process commands within any child windows can be created.

When the Office XP developer Add-in is installed, it automatically sets the VBA Source Code Control add-in to load. This causes the problems with TestPartner. Perform the following steps to resolve this issue:

  1. Start Microsoft Access.
  2. Press ALT+F11. Visual Basic displays.
  3. In Visual Basic, choose Add-in Manager from the Add-ins menu. The Add-in Manager dialog box displays.
  4. In the Available Add-Ins list, select VBA Source Code Control.
  5. Under Load Behavior, clear the Load/Unload and Load on Startup check boxes.
  6. Click OK to close the Add-in Manager dialog box.
  7. Close Microsoft Access and Visual Basic.

TestPartner can now be logged onto and assets can be created without problems or errors.

Referencing VB6.OLB (Visual Basic Objects and Procedures)

Calling any methods, such as Clipboard.GetText(), that are referenced through VB6.OLB, will cause TestPartner to crash and be removed from memory. The issue is a known VBA issue, as opposed to a result of TestPartner's integration with VBA.

Record and Playback

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 select the mode using the IME system tray icon. TestPartner ignores the IME hotkeys and does not record them.

IME Interaction During Raw Record Mode

TestPartner does not support recording of keystrokes in Raw Mode while interacting with an IME. If interacting with an IME while the Raw Record option in TestPartner is set to Yes, input keystrokes are recorded as the IME's interpretation of the keystrokes and not the raw keystrokes.

Character Display for Java Applications When IME Mode is Changed Before Script Playback

If a script is recorded against a Java application where characters are typed into Java controls, then the active Input Method Editor (IME) is changed before script playback, the script will playback properly, but characters may display as question marks (???). This issue occurs because of the way the Java VM processes characters that it receives.

Each character processed by a Java Virtual Machine (VM) is processed using the active keyboard layout for the VM (an IME is considered a keyboard layout). The Java VM assumes that the character has been generated using the active keyboard layout. The Java VM uses Windows API functions that convert the character from it's wide representation to a multi byte representation using the active keyboard layout.

If a Unicode character received by the Java VM cannot be converted using the active keyboard layout, the function that Java uses returns a "?". To avoid this issue, ensure that the IME used during recording is used during playback.

Existing Scripts With Long Class Names

In TestPartner 05.03, the maximum character length for an object's ClassName property has been expanded from 199 to 255 characters. In previous TestPartner releases, if any script contained a object class name over 199 characters, the class name was truncated to 199 characters and the script played back correctly. Because of the expanded character length, scripts recorded in previous TestPartner releases that contained class names over 199 characters may not playback properly in TestPartner 05.03. To work around this issue, re-record any object with truncated class names in scripts that were recorded in previous TestPartner releases.

Recording a Java ComboBox Control With the Wrong Index

TestPartner may incorrectly compute the index for Java ComboBoxes while recording. This causes the recorded script to be unable to attach to Java ComboBox controls during script playback.

To work around this issue, identify the Java ComboBox control while the application is in its playback state, and note the control's index. Then replace the control's index in the recorded code with the index identified for the control. This issue will be fixed in the next generally available release of TestPartner.

Debugging User Forms

When debugging a script that involves a user form, the form may hide and not re-display. To work around this issue, press F5 to regain control of the debugging process.

SAP Support

Modified Property Does Not Return Correct Value

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

Focus for the eCATT Create Object Directory Entry Dialog Box When Saving a BLOB in TestPartner

The Create Object Directory Entry Dialog Box in eCATT does not come into focus after saving a BLOB in TestPartner (using the Save and Go to eCATT menu item). Due to an SAP issue, TestPartner is not able to assign the focus when the dialog box appears.

To work around this issue, click the eCATT application button on the taskbar to bring the dialog box into focus.

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.

TestPartner and the Network Password Dialog Box in SAP

Whenever SAP attempts to access a page outside the firewall, a Network Password dialog box appears. If the Network Password dialog box appears while TestPartner is attempting to enumerate SAP objects during recording or script playback, the script may hang indefinitely. This is because the script must wait for the Network Password dialog box to be dismissed before completing the object enumeration. This will not happen since the script has no mechanism for dismissing the dialog box.

To work around this issue, log on to the firewall in SAP before recording or playing back a script that tests SAP. This can be done by accessing a page in SAP that is outside the firewall and entering a user name and password into the Network Password dialog box when it appears. Once logged in to the firewall, the dialog box will not appear again until SAP is closed and then reopened.

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.

Integrations

Loading Multiple GUI Files Using WinRunner or the TestPartner Tool Domain

GUI files can be loaded programmatically through a WinRunner script or startup script, or can be added through either WinRunner GUI or from the TestPartner Tool Domain. However, problems can occur if a TestPartner Tool Domain loads any GUI file with the same objects as a GUI file loaded in a WinRunner test script or WinRunner startup script. Possible problems include inability to identify objects on a screen or attach statements causing attaches to the wrong object.

To work around this issue, load multiple GUI files from the WinRunner script, the WinRunner startup script, or the configuration file whenever possible. Also, ensure that any GUI files specified in the TestPartner Tool Domain are not also loaded by a WinRunner script, startup script or configuration file.

Installation

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 05.03 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 InstallShield 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.

Licensing

License Administration Utility

After installation of TestPartner with a valid license, there is the possibility that the user may be presented with a window that states that they are using a 30-day trial version of the software. In order to correct this issue and remove this message, the user must launch the License Administration Utility (LAU), verify through the Help>About menu that the version of LAU is 3.3 or higher, and use the utility to reset their license. If the LAU version is found to be 3.2 or lower, there may be two versions of LAU installed. The later version may be found in C:\Program Files\Common Files\Compuware.


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:

Telephone

800.538.7822

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 http://www.compuware.com for information about Compuware customer support policies and problem resolution process.

Mail

Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099

 

End of TestPartner Release Notes
(C) 2005 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States.