Rational TestManager Service Release 2001A.04.02.293.002 Release Notes
Copyright © 2001 Rational Software Corporation. All Rights Reserved.
These release notes describe the
software defects that have been fixed in Service Release 2 for the Rational
TestManager product. Service
Release 2 incorporates all changes that were included in Service Release 1; it
is not necessary to install Service Release 1 prior to installing this Service
Release.
Install this service release if you
are using Rational TestManager without Robot. The archive
testmanager2001A.04.02.293.002.zip contains updates for Windows 9.x, NT, 2000,
and ME. If you are using the Rational TestStudio, TeamTest, or Robot products
or are using TestManager and Robot in other Rational Suites, use the archive
teststudio2001A.04.02.293.002.zip. For updates of UNIX Test Agents, use the archive
unixtestagents_2001A.04.02.293.002.zip.
This service release also incorporates the Service Release 1 update for the Rational Suite Extensibility TeamTest adapter, used by SoDA for retrieving TestManager data, making Test Suites available for reporting. The TeamTest adapter is the TeamTest SoDA domain. This change provides access to Test Suites (Suite artifact type in the TeamTest adapter).
Defects fixed in Service Release 1
Defects fixed in Service Release 2
Contacting Rational Technical Support
There are no changes to the supported platforms in this release. For information on supported platforms, see the Rational Suite Release Notes, Version 2001A.04.00.
There are no changes to the hardware requirements in this release. For information on hardware requirements, see the Rational Suite Release Notes, Version 2001A.04.00.
There are no changes to the software
requirements in this release. For
information on software requirements, see the Rational Suite Release Notes,
Version 2001A.04.00.
Before you install this service release, follow these steps:
1. Stop all Rational products.
When you are installing on the
TestStudio host (non-agent) computer, you must stop the ProxyServer
Service (rtpxsr.exe) if it is running. Do the following:
·
For NT servers:
a)
Select Start->Settings->Control
Panel->Services.
b)
Select ProxyServer
Service.
c)
Click Stop.
·
For Windows 2000:
a) Select Start->Settings->Control Panel->Administrative
Tools->Computer Management.
b) Click Services and Applications.
c) Click Services.
d) Select ProxyServer Service.
e) From the Action menu, click Stop.
2.
Stop the Agent process
for NT and Windows 2000 test agents:
a)
Open Task Manager.
b)
Select the Task Manager
Processes tab.
c)
End the agent process
called rtprvd.exe.
.
To install this service release, follow these steps:
1. If you have downloaded the service release consolidated patch zip
file, rs_2001a.04.02_consolidated_patch.zip, you’ll need to first extract
teststudio2001A.04.02.293.002.zip from it.
If you already have the teststudio2001A.04.02.293.002.zip file, skip
Steps 2 through 5 below and go to Step 6.
2. Go to the folder in which you downloaded the service release
consolidated patch zip file.
3. Open the consolidated patch zip file and select teststudio2001A.04.02.293.002.zip.
4. Extract teststudio2001A.04.02.293.002.zip by clicking on Extract
and specifying a new folder, such a C:\Temp\TestStudio. This extracts
teststudio2001A.04.02.293.002.zip to the folder rs_2001a.04.02_consolidated_patch
contained in the new folder you specified.
5. Go into
the rs_2001a.04.02_consolidated_patch folder in the folder that you specified
in Step 4. For example, C:\Temp\TestStudio\rs_2001a.04.02_consolidated_patch.
6. Extract
the files from teststudio2001A.04.02.293.002.zip into a
new folder named SR2.
7. When the
extraction is complete, select Start->Run and then type cmd.
A command prompt appears.
8. Change (cd) to the SR2 folder that contains the extracted
files.
9. Install
the service release from either the Windows or Windows_Agent folder.
·
Change (cd) to the Windows folder to install
the service release for a local (non-agent) computer and type the following
command:
xcopy /e
/s *.* "C:\Program Files\Rational"
This command copies all service release files into their corresponding
Rational folders. If you originally installed in a folder other than C:\Program
Files\Rational, use that folder name in the xcopy command.
·
Change (cd) to the
Windows_Agent folder to install on a
Windows Test Agent computer and type the following command:
xcopy /e
/s *.* "C:\Program Files\Rational"
This command copies all service release files into their
corresponding Rational folders. If you originally installed in a folder other
than C:\Program Files\Rational, use that folder name in the xcopy command,
Note: On Windows NT and Windows 2000 hosts, both the ProxyServer
Service and agent process are configured by default to start at boot time. If
you do not reboot after installing the service release, restart the ProxyServer
Service on local hosts and the agent process on agent hosts.
This service
release contains a new documentation file, SQLAnywhere.rtf,
related to using a SQL Anywhere Test Datastore. Installation of this service release will place the SQLAnywhere.rtf
file in the Rational Test (%RATL_RTHOME%) directory. This
file provides user documentation for creating a SQL Anywhere Test Datastore as
well as switching a Microsoft Access Test Datastore to a SQL Anywhere Test
Datastore.
ID |
CaseID |
Component |
Description |
RATL00029425 |
484993 |
Robot Session Recording |
Traditional Chinese
character input was not datapooled correctly in VU script |
RATL00039585 |
|
Robot |
Erratic behavior during GUI playback with Netscape scripts recorded
under IE |
RATL00044316 |
697180 |
Robot Session Recording |
Application crash when trying to record DCOM |
RATL00044731 |
|
TestManager |
HTTP VU playback hangs, especially on AIX agents |
RATL00046598 |
739275 |
Robot Session Recording |
Not getting all expected objects during DCOM recording |
RATL00047139 |
747538 |
Robot Session Recording |
DCOM recording fix |
RATL00047360 |
750883 |
Robot Session Recording |
No scriptable protocol from DCOM recording |
RATL00048113 |
|
Robot Session Recording |
DCOM Script generation failure if BSTR longer than 1020 characters |
RATL00048164 |
|
QualityArchitect |
VB Scenario Test Not creating/compiling RES file |
RATL00048175 |
755029 |
TestManager |
Not able to generate reports for playback involving more than one user
on AIX agent |
RATL00048304 |
752798 |
Robot Session Recording |
VU script from Oracle API session generated incorrectly |
RATL00048305 |
752798 |
Robot Session Recording |
VU script from Oracle API session didn’t correctly specify array
parameter variables |
RATL00048548 |
|
TestManager |
When a test case run causes TestManager to launch ManualTest, it
requires the user to login AGAIN to the project if that user has a password |
RATL00048587 |
765583 |
Robot Session Recording |
VU script from Oracle API session incorrectly specified parameters on
sqlexec |
RATL00048857 |
697180 |
Robot Session Recording |
DCOM script generation changes to break BSTR’s longer than 1020
characters into pieces |
RATL00048860 |
769316 |
Robot Session Recording |
Not able to generate script from DCOM session |
RATL00049030 |
|
QualityArchitect |
COM/EJB Scenario Template can’t be found if user logs in as any person
other than the original installer of RQA |
RATL00049360 |
784841 |
Robot Session Recording |
Quotation marks needed around char datatype values in Oracle VU
scripts. |
RATL00049419 |
790567 |
TestManager |
Reports will inappropriately filter out responses with negative
response times |
RATL00049510 |
777148 |
RDSI |
Enhancement to allow SoDA listing of scripts in a suite |
RATL00049712 |
798910 |
TestManager |
Opening a Suite implementation
from the Test Case property sheet causes TestManager to crash |
RATL00049761 |
|
QualityArchitect |
Tests generated
under Japanese NT OS will not compile |
RATL00049929 |
800566 |
TestManager |
Report generation failure on runs involving multiple agents |
RATL00049994 |
793371 |
TestManager |
TestManager crashes when adding test cases to a suite |
RATL00050434 |
|
TestManager |
RQA: Tests generated for COM unable to be run from Test Manager |
ID |
CaseID |
Component |
Description |
RATLC00002364 |
|
QualityArchitect |
COM Scenario template
selection not working from project level Rose Model Default or User Default |
RATLC00002484 |
|
QualityArchitect |
Cannot select template
from Tools menu |
RATLC00003094 |
|
Robot |
Allow borderless MDI
child windows to be recognized as context windows |
RATLC00003295 |
803726 |
Robot Session Recording |
Script generation was terminating
abnormally for an http session. |
RATLC00003355 |
730091 |
Robot Session Recording |
Script generation files
on an API HTTP session due to problems with handling cached cookies. |
RATLC00003361 |
806213 |
Robot Session Recording |
Script generation was terminating abnormally for an API ODBC session |
RATLC00003369
|
|
Robot Session Recording |
Application would crash if DCOM recording attempted without ADO 2.6 |
RATLC00003370 |
800635 |
Robot Session Recording |
VU Script generation was terminating abnormally because of incorrect
formatting of the SQL_DATE in a SQL Server 7 session |
RATLC00004455 |
778099 785427 |
TestManager |
GUI Test Script Files disappear due to datastore corruption |
RATLC00004480 |
803872 |
TestManager |
Unable to connect to project due to corrupt tds.mdb files. |
RATLC00004495 |
804394 |
TestManager |
Only header and footer remain from scripts due to datastore corruption |
RATLC00004585
|
760372 |
TestManager |
Second run of a suite on a VB application causes TestManager to hang |
RATLC00004699 |
|
TestManager |
Some http_requests hang after a couple hundred script iterations due
to thread problems |
RATLC00004871 |
|
TestManager |
Changed the start index on the Status report graph from 0 to 1 to
match the grid |
RATLC00004952 |
|
TestManager |
Test cases distributed over implementation types causes error that
leads to TestManager crash |
RATLC00007687
|
768679 |
Robot |
Robot misses clicking on checkboxes and radiobuttons since offsets
incorrect |
RATLC00007726 |
|
TestManager |
Test cases show as not having an implementation, but their property
sheet shows they are implemented |
RATLC00008082 |
804614 |
TestManager |
Restore the cut & paste feature in the test case design editor |
RATLC00008084 |
|
TestManager |
Fixed various ODBC playback issues |
RATLC00008152 |
818135 |
TestManager |
Unable to connect to project due to datastore corruption |
RATLC00008160 |
802292 |
Robot |
Robot is recognizing editboxes, dropdownlists, and checkboxes in a
table as pushbuttons |
RATLC00008299 |
772672 |
TestManager |
SIGSEGV signal received when running Manual Script |
RATLC00008307 |
732477 |
TestManager |
sqlfetch_cursor command failing with ERROR –1: End of data |
RATLC00008311 |
803187 |
Robot Session Recording |
Problem handling incomplete requests from IE |
RATLC00008367 |
807209 |
TestManager |
General test datastore errors when working with test cases |
RATLC00008383 |
808546 |
TestManager |
Unable to connect to project due to datastore corruption |
RATLC00008397 |
|
Robot |
Restore functionality to recognize DTPicker and Listview controls with
VB/HTML and Robot |
RATLC00008409 |
|
QualityArchitect |
Rose hangs during EJB Unit Test Generation |
RATLC00008415 |
|
TestManager |
Tests generated for COM unable to be run from Test Manager |
RATLC00008456 |
|
TestManager |
Corrected problem with multiple threads overwriting global buffer
during HTTP playback. |
RATLC00008462 |
800149 |
TestManager |
Wrong port used for HTTP connection since port was not specified on
Host field |
RATLC00008527 |
804614 |
TestManager |
Allow copy & paste of lines in Manual Test grid editor |
RATLC00008528 |
804614 |
TestManager |
Multi-select copy & paste of steps/rows in Test Case Design editor
fails |
RATLC00008532 |
779815 |
TestManager |
Fixed potential memory leaks when calling external C routines with
string parameters |
RATLC00008589 |
689985 |
Robot Session Recording |
Recording of API ODBC was hanging if SQLExtendedFetch failed |
RATLC00008808 |
|
TestManager |
TestManager crashes when inserting a test case that’s been deleted
into a suite. |
RATLC00008878 |
821097 |
TestManager |
HTTP playback fails with “chunk decoder received illegal chunk size”
due to multiple threads overwriting global buffer. |
RATLC00008884 |
825156 |
TestManager |
HTTP playback fails with no response received due to multiple threads
overwriting global buffer |
RATLC00008885 |
825005 |
TestManager |
http_nrecv not getting complete response due to multiple threads
overwriting global buffer |
RATLC00008970 |
824832 |
TestManager |
GUI Test Script Files disappear due to datastore corruption |
RATLC00009168 |
829549 |
Robot Session Recording |
Fixed script generation memory allocation error for ODBC session |
RATLC00009205 |
|
Robot Session Recording |
WSNADDR invalidated due to “:” changed to “;” by NuTCRACKER during API
recording |
RATLC00009213 |
826174 |
Robot |
Robot is recognizing HTMLLinks inside nested frames with an incorrect
offset under IE 5.5 |
RATLC00009370 |
829876 |
Robot Session Recording |
Fixed network recording problem with W2K SP2 where gethostbyname() was
returning the loopback addr for the local host. |
RATLC00009393
|
827892 |
TestManager |
Problems with conversion of a V2000 respository to a V2001a project. |
RATLC00009445 |
|
TestManager |
TestManager crashes repeatedly within “Run properties of test case”
dialog when inserting test assets into suite |
RATLC00009605 |
832625 |
Robot Session Recording |
Problem with HTTP Keep-Alive connections using secure proxies. |
RATLC00009632 |
829741 |
TestManager |
Unable to playback GUI script to existing log folder / log due to
datastore corruption |
RATLC00009635 |
830126 |
TestManager |
Unable to connect to project due to datastore corruption |
RATLC00009678 |
835933 |
Robot Session Recording |
Manual filtering dialog doesn’t allow change to Socket protocol |
RATLC00009715 |
836522 |
TestManager |
After run, [1.1.8.201] unlink of local user’s log file u001 failed,
Permission denied |
RATLC00009903 |
835221 |
TestManager |
“Unable to open the test log” error message after playback of shell
script |
RATLC00009917 |
838530 |
TestManager |
Unable to view logs in TestManager due to datastore corruption |
RATLC00009927 |
|
Robot Session Recording |
Get “Method ‘~’ of object ‘~’ failed”
during API recording of DCOM session |
RATLC00010064 |
|
Robot Session Recording |
Some ODBC traffic in .wch file but not in
script |
RATLC00010076 |
834205 |
TestManager |
log_msg() with a very large message (>32K)
causes TestManager to hang due to overrun of event specific data that can be
logged with an event |
RATLC00010132 |
843363 |
Robot Session Recording |
Improvement in SessionID correlations for
HTTP session |
RATLC00010138 |
822314 |
TestManager |
TestManager
crashes when expanding ReqPro requirements/Test Inputs |
RATLC00010189 |
838893 |
TestManager |
Correct
handling of HTTP GET requests with request data. |
RATLC00010322 |
832048 |
TestManager |
IIOP_INVOKE
does not accept strings longer than 2K |
RATLC00010330 |
|
Robot Session Recording |
Problems
with DCOM recording script generation |
RATLC00010451 |
831781 |
TestManager |
http_request
fails with host unreachable when playing back through proxy requiring Basic
authorization |
RATLC00010512 |
812480 |
Robot |
An
object properties verification point on the MsFlexGrid.ocx embedded in a
Visual C++ application doesn’t capture all the object properties. |
RATLC00010514 |
|
Robot |
Fix of
memory leak in RTXVB and RTXOL extensions |
RATLC00010573 |
|
Robot Session Recording |
Support
for process chaining of out-of-proc COM objects |
RATLC00010574 |
|
Robot Session Recording |
DCOM script
generation crashes on multi-dimensional array |
RATLC00010796 |
801671 |
Robot |
VB
application error when recording with Robot |
RATLC00011079
|
835350 |
TestManager |
Not
able to run xcopy from a testcase |
RATLC00011404 |
|
TestManager |
http_nrecv
not getting complete response due to multiple threads overwriting global
buffer |
By incorporating the Service Release
1 update for the Rational Suite Extensibility TeamTest adapter, this service
release gives SoDA limited access to Test
Suites. This adds two selectors to the
Test Manager domain for SoDA. It
includes the following:
o From a
Test Case artifact:
a) Right
click a TestCase from a defined Test Plan
b) Select
Properties
c) Click
the Implementation tab
d) Click
the Select button from the Automated implementation group
e) Select
Suite from the drop down menu and select the desired suite
f) Click
OK to close the Properties dialog box
o From a
Suite artifact:
a) Click
File->New Suite
b) Select
the Functional Testing Wizard
c) Click
the Select button on the Functional Suite Wizard
d) Select
any defined Test Cases
e) Click
Next to continue and finish creating the suite
o Automated
Script:
a) Right
click a TestCase from a defined Test Plan
b) Select
Properties
c) Click the
Implementation tab
d) Click
the Select button from the Automated implementation group
e) Select
the GUI or VB type
f) Select
a Robot script from the list
o Manual
Script:
a) Right
click a TestCase from a defined Test Plan
b) Select
Properties
c) Click
the Implementation tab
d) Click
the Select button from the Manual implementation group
e) Select
the desired script
f) Click
OK to close the Properties dialog box
NOTE: this selector does NOT retrieve
information from Manual Scripts. In the
SoDA TemplateView, the ImplementingScript selector provides a sub-relationship
named "ManualSteps," but it retrieves blank information.
common\RSETeamTest.dll
Rational
Test\QualityArchitect\reiservices.dll
Rational
Test\QualityArchitect\rtCTGUI.dll
Rational
Test\QualityArchitect\rtscenariotestgenerator.dll
Rational
Test\QualityArchitect\rtunittest.dll
Rational
Test\bin\CS\DYNA\rtsvui.exe
Rational Test\bin\rtaagt.exe
Rational
Test\bin\rtpsrv.exe
Rational
Test\msg\C\ratl_prvu.dat
Rational
Test\msg\C\ratl_tmsserver.dat
Rational
Test\shlib\iiop\libiiop.dll
Rational
Test\shlib\sql\libodbc.dll
Rational
Test\shlib\sql\libsqlserver.dll
Rational
Test\shlib\web\libhttp.dll
Rational
Test\tsea\rttseacmd.dll
Rational
Test\datastore.cab
Rational
Test\datastore.lst
Rational
Test\pthreadVSE.dll
Rational
Test\rtarpt.exe
Rational
Test\rtasrv.exe
Rational
Test\rtcomtestserver.dll
Rational
Test\rtconversion.exe
Rational
Test\rtfact.exe
Rational
Test\rtlogio.dll
Rational
Test\rtmanager.exe
Rational
Test\rtmanualtest.exe
Rational
Test\rtnnet.dll
Rational
Test\rtplay.dll
Rational
Test\rtprvd.exe
Rational
Test\rtprvu.exe
Rational
Test\rtrec.dll
Rational
Test\rtreqproadapter.dll
Rational
Test\rtrvs.dll
Rational
Test\rtsgen.exe
Rational
Test\rtsgenw32.dll
Rational
Test\rtssrv.exe
Rational
Test\rttestserver.dll
Rational
Test\rttss.dll
Rational
Test\rtvsrv.exe
Rational
Test\rtvui.exe
Rational
Test\rtxcomspy.dll
Rational Test\rtxie.dll
Rational
Test\rtxmj.dll
Rational
Test\rtxnv.dll
Rational
Test\rtxodbc.dll
Rational
Test\rtxol.dll
Rational
Test\rtxrbutil.dll
Rational
Test\rtxsys.dll
Rational
Test\rtxutil.dll
Rational
Test\rtxvb.dll
Rational
Test\rtxvspy.dll
Rational Test\wwwapp.dll
Rational
Test\wwwcache.dll
Rational
Test\wwwcore.dll
Rational
Test\wwwdir.dll
Rational
Test\wwwdll.dll
Rational
Test\wwwfile.dll
Rational
Test\wwwhtml.dll
Rational
Test\wwwhttp.dll
Rational
Test\wwwmime.dll
Rational
Test\wwwstream.dll
Rational Test\wwwthread.dll
Rational
Test\wwwtrans.dll
Rational
Test\wwwutils.dll
Rational
Test\datastore.mdb
Rational Test\SQLAnywhere.rtf
Rational
Test\tds.db
Rational
Test\tds.log
Note for SQL Anywhere users on Windows 2000: To avoid potential problems with connecting
to a SQL Anywhere datastore, it is required that you rename the file iphlpapi.dll to iphlpapi.dlx in the Rational Test directory.
Note for Java Enabler users: This service release does not include any updates to the Java Enabler. You can download the latest version of the Java Enabler by using the Web Update selection when running the Java Enabler. For example, select Start->Rational Suite TestStudio->Rational Test->Java Enabler.
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:
·
Your name,
telephone number, and company name
·
Your
computer's make and model
·
Your operating
system and version number
·
Product release number and serial number
·
Your case ID number (if you are following up on a
previously-reported problem)