top of page

Overview

 

Updating a raw script with parameters is a critical process in preparing LoadRunner scripts for a load test. It usually consumes most of the time of a scripter during the period of a project where time is critical. Any process to reduce this time increases the productivity of the scripter.

 

If a script needs to be re-recorded, the parameters normally need to be re-applied each time, often manually.

 

DoxRunner significantly reduces scripting time by providing a framework for documenting parameter rules in such a manner that they can be applied automatically to a raw script by the DoxRunner Process Raw operation, reducing manual intervention.

​

DoxRunner categorizes parameter rules into 4 groups:

​

TestDataParameters

 

Test data operations

​

TextDataFiles

DoxRunner's Test Case and Script operations support three types of test data:

  1. Text Data Files;

  2. LoadTest Database;

  3. Virtual Table Server (VTS).

​

 

Text Data File parameter operations

 

A Text Data File parameter is LoadRunner's native method of handling data. DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

LoadTestDatabase

 

LoadTest Database parameter operations

 

The LoadTest database option for managing data uses a MySQL database. It is superior to Text Data File and VTS. Although native LoadRunner doesn't support this method, DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

VTS

 

Virtual Table Server (VTS) parameter operations

 

VTS is LoadRunner's alternative to Text Data FilesDoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

CorrelationRuleParameters

 

Correlation rule operations

​

BoundaryCorrelation

DoxRunner's Test Case and Script operations support two types of correlation rules:

  1. Boundary Correlation Rules;

  2. Regex Correlation Rules.

​

RegexCorrelation

​

Boundary Correlation rule operations

​

A Boundary Correlation Rule is a template for preparing one or more web_reg_save_param_ex functions. DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

OtherParameters

 

Regex Correlation rule operations

​

A Regex Correlation Rule is a template for preparing one or more web_reg_save_param_regexp functions. DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

 

Other parameter operations

​

Custom

DoxRunner's Test Case and Script operations support four other types of parameter rules:

  1. Custom parameters;

  2. Data / Time parameters;

  3. Random Number parameters;

  4. Additional Attributes.

​

 

Custom parameter operations

 

DoxRunner's Process Raw operation reads the Custom parameter rules from the Test Case and the Solution document and applies them to a raw script.

​

DateTime
RandomNumbers

 

Date / Time parameter operations

 

As expected, a Date / Time parameter manages dates and/or times. DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

AdditionalAttributes

 

Random Number parameter operations

 

As expected, a Random Number parameter manages random numbers. DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script.

​

 

Additional Attribute operations


An Additional Attribute allows a performance tester to assign a value to a parameter via a scenario in Performance Center or a Controller without needing to update any of the scripts, so long as the scripts recognize the additional attribute and can parameterize it.

 

DoxRunner's Process Raw operation reads the rules from the Test Case and the Solution document and applies them to a raw script in two steps:

1. Create the Additional Attribute in the Runtime settings using the Name and Value;

2. Extract the value from the Additional Attribute in vuser_init.c;

3. Assign the value to the specified parameter name at the same place in vuser_init.c.

​

bottom of page