(8) How the script list script in the query session is included in a session
Query a list of scripts in a session:
1. In TestManager, press View --Test Asset Workspace.
2. Double-click on the session queries. ALL
3. Double click to view the session name of the script.
Press CONTAINED SCRIPTS.
(9), use the session to generate scripts
A session regeneration is a script
For a variety of reasons, you want to regenerate into a session script, for example: you want to discard the original script or want to regenerate scripts for different script generation options.
When regenerated in a session, the initial script is covered with a new script, and the original script is applied in the recycled script.
At any time, you can use the following methods to regenerate the script:
1. In Robot, press Tools --- Regenerate Test Scripts from session.
2. Select the session name you want to regenerate.
3. Press OK
Generating a script dialog box appears. It reflects the process of automatic regeneration scripts. After a period of time, the script is completed, and the successful completion information appears in the status bar. OK button is hit.
Note: When the regeneration test foot from the session dialog is determined, this script in the session is destroyed. If you have a regeneration script, Robot will generate some empty scripts before regenerate scripts.
4. Press OK to confirm that the script is regenerated.
(10) integrating VU scripts into the session
A session integrates multiple scripts
1. During the session entry, you want to end a script and start the new script, and click the Split Script dialog box.
2. Define or select the script name or accept the default name at the time of the end. You can give up your requirements until you start entering the current script, hit the IGNORE JUST-Recorded Information. This action only affects the current script. The script that is previously recorded for the same session is invalid.
3. Press OK
4. Repeat the above steps multiple times.
5. End the recording, define or select the script name or accept the default name.
(11), manual VU script code
To date, the fastest and easiest way to generate the VU script is to let Robot record customers and automatically generate scripts.
You can also open an empty VU script and add code to him. Such as: You are manual code, or copy the encoding from other scripts.
step:
1. Hit File in Robot --- New --- Script.
2. Define or select the script name or accept the default name
3. Hit VU
4. Hit the OK button, Robot generates an empty script as follows:
#include
{
}
5. Add code to the VU script.
Session Record Options dialog - Generate Sign
This logo can set a variety of script generation options
Open: Press Tools - Session Record Options. Press the Generator Sign
Can do:
A Automatically add DataPool commands with DataPool_config declarations (click Tools - Session Record Options. Press Generator to select Use DataPools. Press OK.)
B Dispatch A Command ID Prefix (You cannot use this option to define multiple Command ID prefixes to stop the last Command ID prefix before the record is used for Robot generated scripts.)
C Inserts the row to the script. Select any value of Display Recorded Rows.
---- none. No return line to the script.
---- first. From the server inserted the number or row of the data specified by the data. Specify the number of bytes or rows with neighboring domains.
--- Last inserts the number of rows from resetting the end of the record. --- ALL inserts all returns to the script.
D is influenced by SQL Statement or web server to insert bytes or rows. Press Tools - Session Record Options. Press the Generator flag to select Verify Playback Row Counts.
E Insert the code returned by SQL Statement. Select Verify Playback Return Codes.
F Bundle The expression output parameters. Select Bind Output Parameters to Vu Variables check box. When the selection, it will generate the output parameter returned to the VU script to return variables. This application only supports output bundled parameters.
G Controls VU script playback speed.
--- per command. VU script playback speed is based on the actual time required for each emulation command. Requirements.
--- Per scrip. VU script playback speed is based on all emulation command. The average time required for recording and processing. All Emulation Command thinks time with the same average delay.
--- None. VU script playback speed is based on the respective script speed, the default is 5 seconds.
H Set the CPU / User, select the CPU / User Threshold (MS) check box, specify the CPU / user with milliseconds
I. Set the biggest thinking time, specify the biggest thinking time with milliseconds.
