Command Trace
364
Chapter 12 - Reporting Performance Testing Results
For each virtual tester, the Command Trace report lists the following information:
s
A line showing the virtual tester that is being reported. In this example, the tester
is Data_Entry[1], or the first virtual tester in the Data Entry group.
s
Default TSS environment variable values and environment variable changes
taking place on each virtual tester during playback. The changes correspond to
environment control commands executed during the suite run.
Note:
The default setting logs essential--but not all--environment variables. This
information is generally sufficient for reporting purposes. However, to report on all
environment variables, open a suite, click
Suite > Edit Settings,
click in the
TSS
Environment Variable
column, and click the Logging tab. Select the Environment check
box, and then rerun the suite.
The Command Trace report lists the following information:
s
A test script header, which lists the virtual tester, the release, and the name of the
test script.
s
Beginning Timestamp
The time, in milliseconds (since the beginning of the suite
run), at the start of execution of each test script.
s
Login Timestamp
Recorded for each virtual tester. This corresponds to the time
when the virtual tester's logon status changed to
ON
.
s
Emulation commands executed during the suite run. A three-line heading appears
if any emulation commands are included. The Command Trace report gives the
following information for each emulation command:
Src Line
The line number of the command in the source file, if available (Java and
Visual Basic test scripts do not make this value available; therefore, the Command
Trace report displays
N/A
).
Cmd Count
A running tally of the number of emulation commands executed in a
test script. This tally includes
http_request
commands that are read from the
cache. The report shows 0 for SQABasic timers.
Clnt
The value of the
Server_connection
environment variable associated
with each SQL, HTTP, or socket emulation command. If your test script has
multiple connections, this value lets you know which receive command
corresponds to which request. The Command Trace report leaves this column
blank for other commands.
Attached to Server
For TUXEDO sessions that start with a
tux_tpinit
emulation command, this line appears.
