background image
<< Changing the Reports That Run Automatically | Command Data Reports >>
<< Changing the Reports That Run Automatically | Command Data Reports >>

Changing the Reports That Run from the Report Bar

Types of Reports
What's in Command Data Reports?
Command Data reports contain the following information:
Header and trailer lines, which show you which virtual tester generated the data. In
the following example, the header and trailer lines show data from the first virtual
tester in the Accounting group, Accounting[1]:
==> Start of data for virtual tester Accounting[1] <==
==> End of data for virtual tester Accounting[1] <==
Inside the header and trailer lines, the Command Data report shows data on each
command that a virtual tester executed. For example:
*** cmd[cmdID]: script=scrname(cmdcnt), source=srcname(srcline) [con-num]***
actual data written to test log
The command recorded and played back successfully.
An expected error. Indicates that an error occurred during recording and
the same error occurred during playback. For example, during recording,
you attempt to access a Web site that doesn't exist. During playback, the
virtual testers attempt to access the same Web site. This is an expected error,
because it occurred during recording and during playback.
No error occurred during recording but an error occurred during playback.
The command name from the log event.
The command ID from the log event.
The name of the test script.
The number of commands that have been executed in the test script.
source=srcname In most cases, this is the same as the test script. However, if a test script calls
another script or contains an include file, the calling test script or the file
that contains the include directive is displayed.
The source line.
The value of the
environment variable
associated with each SQL, HTTP, or socket emulation command.