|
Rational Robot FAQ
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
How to Finding the Session Associated with a Script?
1. In Robot, click File > Open > Test Script.
2. Click the name of the script whose associated session you want to view.
3. Click Properties.
4. Click General.
5. View the session name in Referenced Session.
How Timers Work?
1. Start the timer (click Insert--Start Timer) just before you click the button to
send the query. This action inserts the VU emulation command start_time
into the script.
2. Stop the timer (click Insert --Stop Timer) as soon as the results appear. This
action inserts the VU emulation command stop_time into the script.
What's a block?
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.
What's a block's 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;
Typically, the start_time 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.
For example, in the VU language:
http_header_recv ["BlockName002"] 200;
When you end a block, command IDs are constructed as they were before you
started the block. For example, if the last command ID before the block was
Script025, the next command ID after the block will be Script026.
- A block ends with a stop_time command plus a comment. For example, in
the VU language:
stop_time ["BlockName"]; /* Stop_Block */
- A script can have up to 50 blocks.
Why Use Blocks?
. To associate the block and timer names with the emulation command that
performs the transaction.
. To include the block name in TestManager reports, thus enabling you to filter
the reports with the block name.
.To make the script easier to read, and to provide an immediate context for a line
within the block through command IDs.
How to insert a block into a script?
- If the Session Insert floating toolbar is not already displayed, click the Insert
button on the Session Record floating toolbar.
- Click the Start Block button at that point in the script where you want the block
to begin for example, just before you start to record a transaction.
- Type the block name.
Robot uses this name as the prefix for all command IDs in the block. The
maximum number of characters for a command ID prefix is seven.
- Click OK.
- Record all of the client requests in the block.
- Click the Stop Block button to end the current block, and click OK.
- Continue recording the other sections of the script.
When you start and stop a block during recording, the commands are reported as
annotations in the Annotations window.
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
| 