DoxRunner
Macquarie University Student Accommodation
VTS Operations
Overview
​
This page shows how DoxRunner Process Raw operation handles VTS rules from preparation, documentation, and how they are applied to a raw script. resulting in a script that is configured with VTS rules and their associated parameters.
​
Prepare
​
If any text data files can be pre-populated, then prepare them.
​
Document
The test case is the preferred place for documenting text data file rules.
The Solution document can also play a role.
​
Record
Text data file parameters are not configured during recording.
​
Process Raw operation
The Process Raw operation presents the documented text data file rules to the scripter along with appropriate values from the script in a green screen. The scripter is then required to match the two using a simple point and click process.
​
The parameters associated by the scripter in the green screen are applied to all relevant values in the raw script.
​
If the text data file exists in the Included Files folder, it is copied into the script's folder. Otherwise a new file is created.
​
Tailor
​
The scripter has a number of activities to do before the script is complete.
How it works - in brief
​
The key to applying documented VTS rules to a raw script is the Process Raw operation (see below).
Before initiating it, become familiar with items to first.
​
Prepare VTS environment
​
Make sure that the VTS environment has been prepared in accordance with the given by the current LoadRunner vendor.
​
Document the rules
The test case is the preferred place for documenting VTS rules.
The Solution document can also play a role.
​
Record the raw script
LoadTest Database parameters are not configured during recording.
​
Initiate the Process Raw operation
During the execution of the Process Raw operation, the documented LoadTest Database rules are presented to the scripter in the green Parameter Association screen, along with appropriate values from the script. The scripter associates the two using a simple point and click process.
​
Values are parameterized
​
All relevant values in the script are parameterized as specified by the scripter in the green Parameter Association screen.
​
Script-specific functions are prepared
​
Skeleton functions are added to the DatabaseOperations.c file depending on the documented table/operation configuration. A InitializeDatabase() function is also created.
​
Initialization code is prepared
​
A call to the InitializeDatabase() function is inserted into vuser_init.c.
​
Manually tailor the script
​
The scripter should check the resulting script, in particular the script-specific functions in DatabaseOperations.c.
For example. if there are script-specific functions that contain a Where clause, these need to be manually completed.
Also, calls need to be made to the script-specific functions, and inserted at relevant places within the main script.