DoxRunner

Point and click parameterization

When initiated, the Process Raw operation will prepare the green screen shown below.

A list of name-value pairs identified from the raw script is displayed on the left.

Seven parameter rule categories from the test case are displayed on the right.

Associate as many name-value pairs to as many parameter rules as you can.

Add more parameter rules if required - the test case will be updated accordingly.

Delete any parameter rules that are no longer required - the test case will be updated accordingly.

Process raw operation

The Process Raw operation is the key script efficiency enabler.

It combines the documentation and a raw script to produce an updated script that is parameterised, formatted, and documented in accordance with the test case documentation.

​

About the result

Applying the Process Raw operation to a newly recorded raw script will result in the following actions:

1. Safety

   • A copy of the raw script is placed in a sub-folder of the script called ArchivedByVUGenScriptSupport;

   • When finished, a copy of the updated script is also placed in this folder (in case subsequent manual updates cause serious errors).

2. Parameterisation

   • Values across the whole script are automatically parameterised according to the Custom Parameters section(s);

   • Values selected by the scripter are automatically parameterised according to the Text Data File  section(s);

   • Values selected by the scripter are automatically parameterised according to the LoadTest Database section(s);

   • Values selected by the scripter are automatically parameterised according to the Date/Time section(s);

   • Values selected by the scripter are automatically parameterised according to the Additional Attributes section(s);

   • Values selected by the scripter are automatically parameterised according to the Random Numbers section(s);

   • Values selected by the scripter are automatically parameterised according to the VTS section(s);

   • Rules from the Correlation Rules section(s) are automatically applied and parameterised.

3. Runtime Settings

   • Rules from the Additional Attributes section are automatically configured in the RunTime Settings and converted to a parameter in vuser_init;

   • The Think Time range as specified in the Configuration section is automatically applied.

4. Data

   • Text data files are configured in the script to match the Text Data File rules;

   • The script is configured for any VTS rules;

   • If relevant, the script is instrumented for the LoadTest Database (by creating a DatabaseOperations.c script file)

     • Skeleton functions for the LoadTest Database are prepared in accordance with the LoadTest Database rules

5. Timers

   • The start transaction timers are converted from the single integer, used during recording (discussed above), to a full name.

     • The full name is formatted using a combination of the Timer Name documented in the Timers section of the test case and the Timer Template CI as specified in the Configuration section;

   • End transaction timers are automatically created and inserted after the last request of the relevant transaction timer;

   • The Timers section has a Phase column.

     • Steps with Phase Log In (LI) or To Iteration(TI) are automatically extracted from Action.c so that they are executed when vuser_init is executed;

     • Steps with Phase Iteration (I) remain in Action.c;

     • Steps with Phase Log Out (LO) are automatically extracted from Action.c so that they are executed when vuser_end is executed.

   • If selected, a common transaction timer is wrapped around the normal timers. This allows the Analysis process to group similar timers over multiple scripts together for better analysis;

   • If selected, an end to end transaction timer is wrapped around all steps in Action.c.

6. Other

   • A web_reg_find function is inserted prior to the first request of a step in accordance with the value defined in the Validation column of the Timers section;

   • All recorded Think Times are removed and replaced by the value defined in the Timers section;

   • If selected, cookies, extra resources, and referrer attributes are commented out;

   • If there is a login function defined in any script file, Session Management elements are configured as follows:

     • A file called SessionManagement.c is created and incorporated into the script;

     • login and logout functions are placed in the SessionManagement.c file;

     • The logout and login functions are called on iteration failure to make it more likely that subsequent iterations start at a known execution point.

   • Files in the Included Files folder are copied into the script:

     • If the file has extension of .c it will be configured as an Action;

     • If a file has an extension of .dat or .txt, it will be copied into the script if, and only if, it is represented by a Text Data File rule;

     • Otherwise it will be configured as an Extra File (for example .dll files).

7. Documentation

   • Sections on the front page of the test case are automatically copied into vuser_init as script documentation;

   • Timers are clearly delineated by a distinctive comment:

     • The distinctive comment is followed by the contents of the Expected Result column from the Timers section;

     • The Expected Result text is followed by text from the NFR section.

   • All parameterised values are followed by a comment giving the original value (appended to the end of the line);

   • All parameter assignments are followed by the text from the Description column of the relevant test case table.

8. Formatting

   • Long lines of attribute pairs are split into separate lines - one line per pair - for easy visual analysis;

   • Some functions that VUGen places on separate lines are reformatted onto one line;

   • VUGen places a blank line between some functions with the same name - the blank line is removed.

​​