Rational TestManager
Release Notes
Release 2001A.04.00
Copyright © 2001 Rational Software and its subsidiaries. All rights reserved.
May 2001
Scope--Product Definition
Getting Started
- Installation Information and System Requirements
- Installation Issues
- Installing on German Windows 98
- Evaluation Artifacts
- Before you Install
- Upgrading from Rational Test 6.x to 7.x
New and Changed Features
- Importing a Manual Test Script from a Test Case Design
- Running Test Cases Associated with an Iteration
- New Test Case Icons
- Running Suites from the Command Line
- Enhancements to Test Case Distribution and Trend Reports
- Executing a Test Case with a Manual Implementation from a Web Browser
- Support for DYNIX/ptx Agents
- Support for New Software Environments
Late Changes to Documentation
- Installing Rational Testing Products
- Using Rational TestManager Manual
- TestManager Copyright Notices
- Rational ClearQuest Multisite
- Using the Analog Report Utility
- Entering Java Compiler Options
- Default Group Status of New Test Users
- Preconditions Set on Test Cases vs. Preconditions within Suites
Guidelines and Restrictions
- Supported Agents
- No TSS Proxy Support for Visual Basic or Java Test Scripts
- VU Test Script Playback
- Command Line Test Script Playback
- Manual Test Script Playback
- Running Java Test Scripts from TestManager
- Windows Example
- Solaris Example
- Renaming Test Plans
- Check Suite When Saving Option
- F5 (Refresh All) Does Not Work in Test Asset Workspace
- Viewing Properties of VU Test Scripts
- Monitoring Options
- Resource Monitoring
- Executing Test Cases on Agents
- Response vs. Time Reports
- SAP Limitations
- BLOB Transfer Unsupported
- Suspended Users in Transactors
- Oracle Testing Limitations
- ODBC Limitations
- Named Pipes Unsupported for Network Recording
- Visual Basic and Java Test Scripts
- Setting the Madge Token Ring Card to Gather Traffic Statistics
- About PeopleSoft Certificates
- Testing CORBA Applications
- IDL
- Recording
- Test Script Generation
- Playback
- Supported and Unsupported Data Types
- UNIX Agents
- SQL Anywhere Server
- Rational Administrator
- Unified Change Management (UCM)
Defects/Change Requests
- TestManager--Visual Basic Support
- TestManager--Java Support
- TestManager--Suites Converted from Schedules
- TestManager--PDF Manual for tsscmd
Contacting Rational Technical Support
About These Release Notes
These Release Notes provide information that is not available in the printed documentation or the Help for Rational TestManager.
Scope--Product Definition
This release incorporates several enhancements to the Rational TestManager product.
Getting Started
Installation Information and System Requirements
You will find complete installation instructions and system requirements in the Installing Rational Testing Products manual, which is available as a printed book and electronically as a PDF file on the Rational Solutions for Windows Online Documentation CD, which also includes a version of the Acrobat Reader.
Installation Issues
Installing on German Windows 98
If you install Rational Suite Enterprise on German Windows 98, you may see the following error message prior to rebooting:
A system error occurred while copying <CD-ROM Drive>:\coverage98\win98\testfactory.mkr to <Destination Drive>:\coverage98\testfactory.mkr: Zugriff wurde verweigert.
You can ignore this message since the file in question, testfactory.mkr, is not needed to run Rational applications and does not corrupt the install.
Evaluation Artifacts
Evaluation artifacts are not included as a part of this installation procedure. As a result, when you select the Evaluator option on the Software Use page of the Rational Software Setup program, sample data will not be installed.
To obtain the sample data, download the Rational Suite Tutorial from http://www.rational.com/documentation.
Before you Install
Before you install the current Rational testing product(s), you must uninstall any earlier versions of Rational Suite PerformanceStudio and Rational LoadTest.
Note: Rational LoadTest functionality is now included within Rational TestManager. Previous versions of Rational LoadTest will not work in conjunction with any testing products from the current release and must be uninstalled before installing this release.
Upgrading from Rational Test 6.x to 7.x
To upgrade from Rational Test 6.x to Rational Test 7.x, you must install the Rational Test 6.x to 7.x Repository Upgrade Kit. Be sure that the machine you run the upgrade on contains no Rational software newer than 7.x. Installation of Rational Suite 2000 or newer on that machine will cause the Repository Upgrade Kit to no longer function.
New and Changed Features
The following new features have been added to Rational TestManager. For details, see the "What's New in Rational TestManager" topic in the TestManager Help.
Importing a Manual Test Script from a Test Case Design
Lets you easily import a manual test script from a test case design. Use the Implementation tab of the Test Case Properties dialog box or the Configured Test Case Properties dialog box.
Running Test Cases Associated with an Iteration
Lets you select a specific iteration and run all of the test cases associated with that iteration.
New Test Case Icons
Several new icons have been added to the Test Plan window, the Test Inputs window, and the Suite window. These icons indicate whether a test case or configured test case has an implementation associated with it, the type of implementation, and whether it is inherited.
To see a description of the new icons from TestManager, start online Help and select "icons in windows" from the index.
Running Suites from the Command Line
Lets you log into a project and run a suite from the command line. For details, see "Running a Suite from the Command Line" in Chapter 5 of Using TestManager.
Enhancements to Test Case Distribution and Trend Reports
There have been several enhancements to the test case reports.
Executing a Test Case with a Manual Implementation from a Web Browser
Lets you run a test case with a manual test script implementation from a Web browser using the Rational ManualTest Web Execution component of TestManager. For information about installing and configuring a Web server, see the Installing Rational Testing Products manual or the Installing Rational Suites Products manual. For information about running a test case from a Web browser, see the Rational ManualTest Web Execution Help.
Support for DYNIX/ptx Agents
DYNIX/ptx Agents are now supported.
Support for New Software Environments
- Netscape 6 support for performance testing, with the following limitations:
- You cannot test the performance of Web applications that use the Secure Socket Layer (SSL). URLs for SSL applications begin with "https://" rather than "http://".
- When a browser user begins recording an HTTP session, TestManager queries the virtual tester's browser for any cookies stored in the cookie cache and copies this information into a COOKIE_CACHE section inside the script. This is done in order to make playback more accurate with respect to the initial cookie values. This feature is not supported for Netscape 6.
- Solaris 2.8 (8.0) agent support
- JDK 1.3 support for Java test script execution
- VB and Java playback on Win9x and Win Me
Late Changes to Documentation
Installing Rational Testing Products
The Installing Rational Testing Products manual refers to the installation types as Typical, Custom/Full, Compact/Laptop, and Minimal. In this release, Minimal installation is now called Network installation.
This manual also mistakenly claims that Rational ManualTest Web Execution supports Microsoft Me.
Using Rational TestManager Manual
TestManager Copyright Notices
TestManager contains portions of the GNU C Library. Copyright notices for the GNU C Library were not included in the printed documentation for TestManager due to production deadlines. Instead, they are provided in these release notes:
Copyright (c) 1996, 1997, 1998, 1999 Free Software Foundation, Inc.
This file is part of the GNU C Library.
Contributed by Ulrich Drepper, <drepper@gnu.org>.
Copyright (c) 1987, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97 Free Software Foundation, Inc.
Copyright (C) 1996, 1997 Free Software Foundation, Inc.
This file is part of the GNU C Library.
Contributed by Ulrich Drepper, <drepper@gnu.ai.mit.edu>.
Copyright (C) 1996, 1997 Free Software Foundation, Inc.
This file is part of the GNU C Library.
Copyright (c) 1989, 90, 91, 92, 93, 94, 95, 96, 97 Free Software Foundation, Inc.
The GNU C Library and its use are covered under the terms of the GNU Library General Public License, a copy of which may be found in <INSTALLDIR>\Rational\Rational Test\opensrc\GNU_LGPL.txt.
See the README.wri file in the same directory for additional information.
TestManager includes a copy of rtcpp.exe, an executable program based on GNU cpp. Portions of this executable are copyrighted as follows:
Copyright (C) 1997 Free Software Foundation, Inc.
Copyright (C) 1990 Free Software Foundation, Inc.
Copyright (C) 1996, 1997 Free Software Foundation, Inc.
Copyright (C) 1988,89,90,91,92,93,94,96,97 Free Software Foundation, Inc.
Copyright (C) 1986, 87, 89, 92-96, 1997 Free Software Foundation, Inc.
Written by Paul Rubin, June 1986
Adapted to ANSI C, Richard Stallman, Jan 1987
rtcpp.exe and its use is covered under the terms of the GNU General Public License, a copy of which may be found in <INSTALLDIR>\Rational\Rational Test\opensrc\GNU_GPL.txt.
See the README.wri file in the same directory for additional information, including disclaimer of warranty.
TestManager includes a copy of executables which use:
pthreads-win32 - POSIX Threads Library for Win32.
The pthreads-win32 library and its use are covered under the terms of the GNU Library General Public License, a copy of which may be found in <INSTALLDIR>\Rational\Rational Test\opensrc\GNU_LGPL.txt.
See the README.wri file in the same directory for additional information.
TestManager includes a copy of executables which use the W3C libwww library.
Copyright (c) 1994-2000 World Wide Web Consortium, (Massachusetts Institute of Technology,
Institut National de Recherche en Informatique et en Automatique, Keio University).
All Rights Reserved. http://www.w3.org/Consortium/Legal/
The W3C libwww library and its use are covered under the terms of the W3C Software Notice and License, a copy of which may be found in <INSTALLDIR>\Rational\Rational Test\opensrc\W3C_IPR_SOFTWARE_NOTICE.htm.
See the README.wri file in the same directory for additional information.
TestManager includes libiiop.dll, which is based on an implementation of the
Object Management Group's "Internet Inter-ORB Protocol" of Sun Microsystems, Inc.
Copyright (c) 1995 Sun Microsystems, Inc. Printed in the United State of America.
The libiiop.dll library and its use are covered under the terms of the Sun Microsystem Inc.'s Copyright and License, a copy of which may be found in
<INSTALLDIR>\Rational\Rational Test\opensrc\InterOrbEngine_License.txt.
See the README.wri file in the same directory for additional information.
Rational ClearQuest Multisite
In Chapter 6, in the section "About Submitting and Modifying Defects," the note about using Rational ClearQuest Multisite is incorrect. Rational ClearQuest Multisite does not ship with this release of Rational software.
Using the Analog Report Utility
Use the Analog report utility, rtaalg.exe, to display client/server traffic for all virtual testers associated with each VU emulation command in a test script. You can obtain this information from TestManager, one command at a time, but you might find this command line utility more convenient in some situations.
rtaalg -i log_file [-o output_file] [-f]
- log_file is the full pathname of the master log file generated by TestManager for the project. Located inside the Build area of the test datastore, the master log is a file inside the log directory with the same name as the log.
- output_file is the full path of the file that will contain the Analog report. If omitted, the report will be written to file analog.out in the working directory. The file will be created if it does not exist and overwritten if it does exist.
- -f (full) specifies that the report should include all commands. If this option is omitted, only commands that failed appear in the report.
The Analog report contains header and trailer lines showing which virtual tester generated the data contained inside the lines. The following example shows the header and trailer lines for the first virtual tester, Accounting[1], in an Accounting user group:
<<<<<<<<<<Start of Virtual Tester: Accounting[1].>>>>>>>>>>
<<<<<<<<<<End of Virtual Tester: Accounting[1].>>>>>>>>>>
Inside the header and trailer lines, the Analog report shows data about each emulation command that the virtual tester executed. For example:
*** cmd[cmdID]: script = scrname(cmdcnt), source = srcname(srcline) n ***
The following table describes Analog report syntax.
Entering Java Compiler Options
You can enter Java compiler options by doing the following from TestManager:
- Click Tools > Manage > Test Script Types.
- Select Java Script and click the Edit button.
- Under the Options heading at the bottom, in the Options Name column, enter:
- In the corresponding Option Value column, type the option(s). Precede each option by a - and separate options by a space.
The Help for this dialog explains how to do this but contains an error.
_TMS_TS0_JAVA_COMPILATIONSFLAGS is indicated instead of the correct string shown above.Default Group Status of New Test Users
The Using Rational TestManager manual and Help (see the "Projects and the Rational Administrator" topic) say that when a test user is created in the Rational Administrator, it automatically becomes part of the Public test group. This is incorrect. A test user is not part of any test group until it is explicitly assigned to a test group.
Preconditions Set on Test Cases vs. Preconditions within Suites
The preconditions that you set when designing and implementing test cases (discussed in chapters 3 and 4 of Using Rational TestManager) are not related to the preconditions that you set within a suite (discussed in chapters 7 and 10).
A precondition set on a test case is a setup dependency to ensure that a test case can run properly. You can enter text in the field. Although TestManager does not use this field, you can refer to it later. If a precondition is not met, the test case may still meet the acceptance criteria, but the constraints necessary for the test case to run are not met.
A precondition set within a suite must complete successfully for subsequent items at the same level in the suite to run. TestManager uses this field. If a precondition fails, remaining suite items at the same level in the suite do not run.
However, you can relate the two types of preconditions, so that a suite precondition enforces a test case precondition. The following steps give an example of how to do this:
- Set a precondition on a test case.
- Within a suite, insert a test script that checks that the test case precondition is met.
- Within a suite, set a precondition on the test script itself.
Guidelines and Restrictions
Supported Agents
- HP-UX UNIX 10 Agents are no longer supported.
- Support for Linux Agents running HTTP test scripts is limited. You can run only 10 virtual testers on an Agent.
- AIX 4.1 Agents are no longer supported.
No TSS Proxy Support for Visual Basic or Java Test Scripts
The TSSServerStart method starts a Test Script Services proxy server. However, proxy servers are not supported for Visual Basic and Java test script types.
VU Test Script Playback
- Playback of VU test scripts is not supported for Windows Me, Windows 98, or Windows 95, whether the system is a Local computer or Agent computer.
- When VU test scripts are played back on HP-UX, AIX, or Solaris Agents, pass/fail status information is not available in the Test Log window.
Command Line Test Script Playback
- Playback of command line test scripts is not supported for HP-UX and AIX Agents.
- When running command line test scripts or custom test script types that use the command line adapter on Windows NT systems as Agents, TestManager may report test script failure even though the test scripts executed successfully. To avoid this, install Service Pack 5 or Service Pack 6a on the Agent.
Manual Test Script Playback
- Playback of manual test scripts is not supported on any Agent.
- When playing back manual test scripts, be sure to dismiss the Manual Test dialog box before trying to terminate users.
Running Java Test Scripts from TestManager
When TestManager plays back a Java test script, it must be able to load a Java virtual machine (jvm.dll or jvm.so). On Windows systems, the location of the JVM can be specified on the system path. If no JVM is found using the system path, TestManager will attempt to locate one relative to the location of java.exe. On Unix systems, the location of the JVM must be specified using the library environment variable appropriate for your system. For example, on Solaris, you must indicate the location of the JVM using the environment variable LD_LIBRARY_PATH.
Windows Example
Solaris Example
/usr/jdk1.2.2/jre/lib/sparc/classic:/usr/jdk1.2.2/jre/lib/sparc/native_threads
If you fail to specify the location of the jvm, and we are unable to locate it relative to the installation of the JDK, you will receive the following error message at playback:
[1.1.5.172] Execution Adaptor rttseajava: couldn't retrieve test script info for SabreClient (datapath = c:\testscripts): [1.3.9.259]: Java() failed
Not able to find or start JVM (Java Virtual Machine), library jvm or javai
[1.1.4.52] RTmaster run not executed due to fatal workload description errors.
*** RTmaster Exiting (1 error, 0 warnings)
Renaming Test Plans
You can rename a test plan only from the Planning tab of the Test Asset Workspace. The rename will not be completed if the test plan is open.
Check Suite When Saving Option
When working with suites in TestManager, be sure to save a suite before checking it. Accordingly, the "Check suite when saving" option on the Create Suite tab of the Options dialog box should be cleared.
F5 (Refresh All) Does Not Work in Test Asset Workspace
You can press the F5 key to refresh all in the Test Plan window and in the Test Input window. This key does not work in the Test Asset Workspace. You need to right-click a folder in each of the Test Asset Workspace tabs or go to View > Refresh from the main menu to refresh all the Test Asset Workspace.
Viewing Properties of VU Test Scripts
The Test Script Properties dialog box does not reference the Robot session from which the VU test script was generated. To view this information, go to the Session Properties dialog box in Rational Robot to look for the test script as a contained script.
Monitoring Options
Occasionally, Monitor menu items may be unavailable. To access monitoring options in this case, use the Monitor toolbar.
Resource Monitoring
- Monitoring system resources during test runs is not supported for Windows Me, Windows 98, or Windows 95, Local or Agent.
- In order to monitor resources on an Agent computer that is running AIX, you must install the bos.acct package on that agent.
Executing Test Cases on Agents
- Windows Me and Windows 98 are considered equivalent when matching computer configurations against test case configurations.
- When you choose a parallel selector in a suite, the option Use multiple computers to maximize test case coverage is checked by default. The functionality behind this option is disabled for this release. This affects not only configured test cases run in parallel on multiple computers, but also configured test cases run automatically.
- This means that when running configured test cases in parallel on multiple computers, depending on test case order, all configured test cases can not be run even if computers matching defined configurations are available. To work around this, limit running configured test cases to one computer at a time, and repeat over the list of desired computers in sequential order.
Response vs. Time Reports
The Show Resource dialog box for data points in the Response vs. Time report for a Performance Testing Report, refers to the MASTER computer. This should read Local computer.
SAP Limitations
The following list gives SAP testing limitations in TestManager:
- UNIX Agents are not supported for the SAP protocol.
- The personalizing option (the multicolored circle in the upper right of SAPGUI) is not supported.
- Multiple SAP sessions with a single client are not supported.
- Only the active screen is rendered, while SAPGUI sometimes renders inactive screens.
- The control box in table controls is not supported.
- Transaction IQ03 is not supported.
- Automatic logon load balancing, as performed by SAPLOGON.EXE and the SAP Session Manager, is not supported.
- The Manager's Desktop functionality under the "Human Resources" menu is not supported.
BLOB Transfer Unsupported
TestManager does not support BLOB (Binary Large OBject) transfer. If you are recording a Sybase or SQL Server session that transfers BLOB data, the connection is ignored and the generated test script does not refer to BLOB transfer activity.
Suspended Users in Transactors
When you monitor a TestManager suite (formerly called a LoadTest schedule), and suspend a virtual tester in an independent transactor, upon restarting, the tester will try to catch up on the missed transactions. If you suspend a virtual tester in a coordinated transactor, the remaining testers will pick up the slack and try to maintain the desired transactor rate. If the rate cannot be maintained, then as testers are restarted, they will try to catch up on the missed transactions.
Oracle Testing Limitations
The following list gives Oracle testing limitations in TestManager:
- Oracle 8 support is limited to API recording.
- Oracle array support is also limited to API recording.
- To play back Oracle 7 with Oracle 7 libraries on HP-UX, you must set the following environment variable before invoking TestManager:
Set the variable in the Environment tab of the System Properties Control Panel.
ODBC Limitations
When playing back a SQL statement that generates multiple result sets, TestManager logs only the data for the first fetch. The other fetches show the number of rows returned, but does not log the data actually returned.
If a sqlfetch_cursor is run multiple times in a row with ALL_ROWS, and expect rows 0, an error for the second sqlfetch_cursor is generated stating:
ERROR -1: {error} STATE=S1010, CODE=0, MSG=[Microsoft][ODBC Driver Manager] Function sequence error
When logging data returned from sqlfetch_cursor, sometimes the data is truncated and the next SQL command appears on the same line as a row of data. This is a logging problem only; the test script is executing correctly.
Named Pipes Unsupported for Network Recording
Named pipes are not supported for network recording.
Visual Basic and Java Test Scripts
Generated Visual Basic test scripts do not pass script line numbers to TestManager. As a result, the TestManager Script view feature (the Script check box under Tools > Options) does not work with generated Visual Basic test scripts. If you manually add method calls to your Visual Basic and Java test scripts that pass test script line numbers to TestManager, the Script view will work. The relevant methods are TSSMonitor.PositionSet (Visual Basic) and TSSMonitor.positionSet (Java).
Setting the Madge Token Ring Card to Gather Traffic Statistics
For Windows NT only, if you are using a Madge token ring card for network recording, make sure that the Traffic Statistics Gathering option is set to enabled. To enable this option, click Start > Settings > Control Panel, and click the Network icon. Then click the Adapters tab, click the Properties button, and enable the Traffic Statistics Gathering option.
About PeopleSoft Certificates
When TestManager creates test scripts that contain PeopleSoft traffic (Tuxedo or Jolt) it automatically correlates any PeopleSoft certificate information required for proper client authentication during playback. The correlations take the form of string variables, declared with the prefix psft_cert, and various operations on them. The following code shows a typical example of certificate correlation in a PeopleSoft/Jolt test script:
1 sock_send
2 jolt_request(0, jolt_sessionid_1, jolt_handlerid_1, 3,
3 jolt_dataxfer(jolt_sessionid_1, JOLT_CALL_RQST,
4 jolt_setatt_name("GetCertificate") +
5 jolt_setatt_version(1) +
6 jolt_setatt_flags(4) +
7 jolt_setatt_data(
8 jolt_setpar_carray(1,
9 "`000000480102030400000000000002bcffffffff0000001f0004`SCTX"
10 "`0a`JavaClient`02`PS`02`PS`00000000000000150008`SCertReq`0"
11 "2`PS`02`PS`00`"))));
12
13 sock_nrecv ["suzy027h"] jolt_response_header();
14 sock_nrecv ["suzy027b"] jolt_response_body();
15 { string psft_cert_1; }
16 psft_cert_1 = "`" + substr(mixed2hexstring(jolt_getpar_carray(1)), 72, 32) +
17 "`";
18 set Think_avg = 230;
19
20 sock_send
21 jolt_request(0, jolt_sessionid_1, jolt_handlerid_1, 4,
22 jolt_dataxfer(jolt_sessionid_1, JOLT_GETDEF_RQST,
22 jolt_setatt_repname("SVC`2f`StmGetTimeOut")));
23
24 sock_nrecv ["suzy028h"] jolt_response_header();
25 sock_nrecv ["suzy028b"] jolt_response_body();
26 set Think_avg = 240;
27
28 sock_send
29 jolt_request(0, jolt_sessionid_1, jolt_handlerid_1, 5,
30 jolt_dataxfer(jolt_sessionid_1, JOLT_CALL_RQST,
31 jolt_setatt_name("StmGetTimeOut") +
32 jolt_setatt_version(1) +
33 jolt_setatt_flags(4) +
34 jolt_setatt_data(
35 jolt_setpar_carray(1,
36 "`0000005a0102030400000000000002bcffffffff0000002f0004`SCTX"
37 "`0a`JavaClient`02`PS`02`PS`10`"+ psft_cert_1 +
38 "`00000000000017000e`SGetTimeOutReq`02`PS"))));\In lines 15 and 16 a certificate correlation variable, psft_cert_1, is declared and assigned a value based on the contents of a previous Jolt response message. The variable is then properly applied to the contents of a subsequent Jolt request message in line 37.
Because this feature is necessary for proper playback of PeopleSoft test scripts, do not change the contents of the certification correlation variables or change the variable's position within the context of the surrounding message data. Doing so improperly may cause corrupt messages to be sent to the application-under-test, leading to unpredictable results. Should correlation variable manipulation be necessary, however, all automatically scripted variables represent 16 bytes of certificate data, in hexstring form, delimited by single backquotes ("`"), for a total of 34 text characters (16 * 2 + 2). For example, "`664d689999999999c99a9ac9c9c9c9c9`".
Testing CORBA Applications
To test CORBA applications with TestManager, you must have the following software installed:
- Windows 2000 or Windows NT Version 4.0 with at least Service Pack 4
- Visibroker (C++ or Java) Version 3.3 or 3.4
IDL
IDL (Interface Definition Language) defines an application's interfaces, including method names, parameters, data types, and exceptions. You can use IDL to map to many languages for implementation. To record test scripts in Robot and play back test scripts in TestManager with methods, parameter names, and data described in a meaningful way, you must import the application's IDL into TestManager before test script generation.
To import IDL into TestManager:
- Click Tools > Interfaces.
- From the Interfaces dialog box, click Import.
- From the Select IDL File dialog box, browse to find and choose the IDL file to import.
- Click OK.
The information imported is stored in the project for use by TestManager at test script generation and play back. You will not be able to play back test scripts until the IDL has been imported into TestManager.
TestManager stores the IDL information within the project based on the interface name.
If you do not load all the IDL prior to test script generation, some methods may script opaquely. That is, method parameter names will not be listed. Instead, only a single parameter with the name "*" is listed, and all data is asciified hexadecimal.
Sometimes, IDL files will include other IDL files. If include path information is not relative, you may have to specify an IDL include path. You may specify such a path using the IDLINCLUDE environment variable. For example, IDLINCLUDE=d:\myidl;d:\otheridl.
Recording
Recording of CORBA applications is similar to recording of other environments. Both Network and API recording methods are supported.
Before recording, you must select IIOP in the Generator Filtering tab of the Virtual User Record Options dialog box in Rational Robot. IIOP traffic between client and server is used to produce VU test scripts.
Test Script Generation
After recording, a VU test script is produced that describes the interactions between client and server. There are two common IIOP VU emulation commands:
- iiop_bind, which describes how to locate an object that supports a certain interface.
- iiop_invoke, which specifies a method invocation, including parameter names and data.
You can limit the scripting of client traffic to a particular computer using the LT7_IIOPCLIENTIP environment variable. For example, LT7_IIOPCLIENTIP=137.162.195.135.
By default, IDL sequences are scripted with a limit of ten members. You can increase this number using the LT7_DEFAULT_SEQUENCE_SIZE environment variable. For example, LT7_DEFAULT_SEQUENCE_SIZE=20.
In each case, the variable is set in the Environment tab of the System Properties dialog box under the Control Panel.
Playback
Before playback, all interfaces referenced in a test script must have their IDL imported into TestManager.
Special IIOP monitoring states are provided for the state histogram monitor window.
Playback of ASCII hex (opaque) data between computers of differing byte ordering is not supported. Byte ordering specification is marked in the IIOP protocol. It is possible that data may be transferred with big-endian byte order, even on Windows NT systems. This case is more likely to occur if the application is Java. The result is that data specified opaquely in these cases may not play back correctly, even though the recording computer and the playback computer have the same byte order.
Supported and Unsupported Data Types
TestManager supports record and playback of the following data types:
- char
- octet
- short
- unsigned short
- long
- unsigned long
- float
- double
- boolean
- enum
- struct
- union
- array
- sequence
The following data types are not supported, and will result in methods being scripted opaquely if they occur as a parameter data type in a method:
UNIX Agents
Only Solaris is supported for UNIX Agent playback. The Visibroker bind modus is not supported for playback.This limitation means that "Visibroker" cannot be used to locate object references at play back. Therefore, another method, such as reading IORs (Inter-operable Object Reference) from a file, or specifying them explicitly in VU test scripts, must be used to locate objects when playing back test scripts from a Solaris Agent.
SQL Anywhere Server
- In this release, only Rational ClearQuest uses the SQL Anywhere server.
- During the installation of a SQL Anywhere Server, select Replace these files with English equivalents independent of the language environment in which you are working. Microsoft recommends this because selected files must be replaced with their English equivalents.
- SQL Anywhere database treats the \ (backslash) character as an escape character. This causes a translation of the backslash character and the subsequent character as they are added to the database. For example '\\' becomes '\', and '\n' becomes an unprintable character, etc.
Rational Administrator
Unified Change Management (UCM)
If you use Unified Change Management (UCM) with Rational Suite under these conditions:
- You use Rational ClearQuest to manage UCM activities, and
- You place a RequisitePro project or a Rational Test datastore under configuration control
Then make sure that you do not set the UCM policy, "Check Assignment Before Work On". (The default is for the policy not to be set.)
When you set the policy, you cannot work on an activity unless you are the owner of that activity. But in the current implementation of UCM for RequisitePro and Rational Test, an entire team of workers share the same activity. Therefore, if the policy is set, only one person, not the entire team, can work in a RequisitePro project or in a Rational Test datastore.
If the policy is mistakenly set, you will see the error message "Source control could not set activity." To work around this error:
- Start the Rational Administrator and connect to a Rational project.
- Right-click the UCM project and click Properties.
- On the ClearQuest tab, unset the policy.
For further details, see the Using Rational Administrator manual.
Defects/Change Requests
TestManager--Visual Basic Support
- If you encounter memory errors when running VB test scripts, we recommend that you use smaller test scripts. If you generated the test scripts using Rational Robot, see the Using Rational Robot for information on splitting test scripts during session recording. If you created the test scripts manually, try breaking out the functionality into smaller test scripts.
- When Visual Basic is installed to a directory location other than the default, make sure the location of the resource compiler is noted in the PATH.
TestManager--Java Support
- If you place a Datapool config section in a Java Test Script with other than the default access flags, you must call Datapool.open specifying the same flags that are in the DATAPOOL_CONFIG section for the datapool. However, the overloaded method that takes only the name of the datapool will attempt to open the datapool with the default access flags instead of the flags specified in the DATAPOOL_CONFIG section of the test script.You must use the open method that requires specifying the access flags and the flags must agree with the DATAPOOL_CONFIG section.
- TSSSync.sharedVarWait does not time out during test script playback. You must manually guarantee that the condition for which TSSSync.sharedVarWait is waiting eventually is satisfied either by careful test script programming or by changing the value of TSSSync.sharedVarWait in the Shared Variable View during suite monitoring.
TestManager--Suites Converted from Schedules
TestManager may crash when you attempt to run a suite that has been converted from a LoadTest schedule, when that schedule also contains scenarios. For the time being, Rational recommends that you use the following workaround:
For any schedule that contained scenarios, before ever saving or running the converted Suite (that is, the first time you open it for editing) do the following for each scenario:
- Rename the scenario in the scenario section of the suite (not its reference under the user group).
- Create a new scenario with the original name.
- Copy and paste all items under the original (renamed) scenario to the new scenario.
- Delete the original (renamed) scenario.
TestManager--PDF Manual for tsscmd
tsscmd.exe provides a command line interface to Test Script Services (TSS). The PDF manual for tsscmd was inadvertently omitted from the documentation CD. (An HTML manual for tsscmd is accessible from the Start menu.) To obtain a PDF manual, go to www.rational.com and click Support > Documentation. The manual's title is The Command Line Interface to Rational Test Script Services.
Contacting Rational Technical Support
If you have questions about installing, using, or maintaining this product, contact Rational Technical Support as follows:
Note: When you contact Rational Technical Support, please be prepared to supply the following information:
| Rational Software Corporation http://www.rational.com support@rational.com |