Visual Basic scripts
Adding Features to Scripts
The following are the timer commands for VU scripts:
Starts timing the activity. Insert this command immediately
before the first emulation command for the activity that you are timing. The
measurement includes the think time (if any) for the next
emulation command in the script.
To exclude the think time for an emulation command, insert
after the emulation command and use the
read-only variable. For
http_request ["test1.001"] ...
start_time ["timerid"] _fs_ts;
Stops timing the activity. Insert this command immediately after
the last emulation command for the activity that you are timing.
For information on using timers in VU scripts, see the
the VU Language Reference.
For information on using timers in Visual Basic scripts, see the
method in Rational Test Script Services for Visual Basic.
For information on using timers in SQABasic scripts, see the
command in SQABasic Language Reference.
A block is a set of contiguous lines of code that you want to make distinct from the
rest of the script. Typically, you use a block to identify a transaction within a script.
A block has the following characteristics:
A block begins with the comment. In the VU language, a block begins like this:
/* Start_Block "BlockName" */
Robot automatically starts a timer at the start of the block. In the VU language,
the timer looks like this:
start_time ["BlockName"] _fs_ts;
emulation command is inserted after the first
action but with an argument to use a read-only variable that refers to the start of
the first action.
The ID of every emulation command in a block is constructed the same way--
that is, by the block name followed by a unique, three-digit autonumber.