top of page
TopOfPage

 

Document the VTS Rules

 

Overview

​

One of LoadRunner's methods of handling test data is the use of VTS and is one of the three methods of managing data supported by DoxRunner.

​

As well as providing a mechanism for documenting VTS rules, DoxRunner saves a scripter's time when re-recording a script by using those documented rules to instrument a raw script using the Process Raw operation. Although all functions can be documented, only four are supported by the Process Raw operation.

​

​The illustration on the right shows how they are configured in LoadRunner.

​

The illustration below that shows how they are configured in a DoxRunner document.

​

The rules are contained in a VTS section of either a Test Case or the Solution document.

​

The important components are the Parameter name and the Configuration, as described below.

​

Parameter

​

The Parameter name is mandatory. It must be unique and only appears in the column with heading Parameter in the table of any VTS section.

​

It must also conform to LoadRunner rules.

​

Overview

Configuration

​

The Configuration is mandatory. In the context of VTS rules,

it must contain two Configuration Items (Function and

Column) as described below and illustrated on the right.

Configuration

1. Function

​

The name of a VTS function is required. It can be preceded by the Configuration Item ID 'Function: ' if the context is not clear.

There is no need to prefix it with "lrvtc_" - it's optional..

​

These functions are supported by the Process Raw operation:

  • retrieve_message

  • send_message

  • update_message

  • query_column

​

2. Column

​

The Column Name is required only if it is different to the Parameter. If it is omitted, then the Parameter name is used as the Column name.

​

It can be preceded by the Configuration Item ID 'Column: ' if the context is not clear.

​

SectionManagement
Column
ScriptConfig.gif
Example.gif
Parameter

 

Section Management - VTS

​

Common Characteristics

​

A VTS section is optional, is semi-structured, and may appear in three places:​​

​

Each instance of the VTS section consists of:

  • a Section Title;

  • a Bookmark;

  • free-form Body Text;

  • a Table with a minimum of two columns (Parameter and Configuration).

​

The Bookmark:​

  • Mandatory;

  • Location: Immediately before the Section Title;

  • Structure: Depends on which document it is embedded in:

​

The Section Title:

  • Mandatory;

  • Location: immediately after the Bookmark;

  • Structure: Free-format text;

  • Style: I_Heading n or I_Appendix n, where n can be an integer from 1 to 5;

  • Length: Cannot be longer than 200 characters.

​

The Body Text

  • Optional;

  • Location: between the Section Title and the Table;

  • Structure: free-format text;

  • Style: I_BodyText;

  • Length: Cannot be longer than 1,000 characters.

​​

The Table:

  • Mandatory;

  • Location: immediately below the Body Text (or Section Title if there is no Body Text):

  • A minimum of two rows:

    • A Heading row and a Data row (one data row per rule);

    • If there are no rules, the last Data row can contain empty cells (or the section can be deleted);

  • A minimum of two columns:

  • All cells in the Parameter and Configuration columns must conform to specific rules, as described in the Overview above.​

​

Advice
Common Characteristics
TestCaseSection

​

Advice

​

Assess whether the section is necessary. This decision will need to take into consideration three factors:​​

  1. Whether the VTS environment is set up;

  2. Whether the Test Case needs VTS rules;

  3. Which scenario you have chosen when assessing the relationship between Test Case sections and Solution document sections.

​

Assess the Section Title and update it if necessary.

​

Make sure the table has the two mandatory columns (Parameter and Configuration), each with the specified heading text.

​

Assess the table to see whether more columns are appropriate, especially a Description column.

​

Assess the Body Text between the Section Title and the Table and update it if necessary.

​

Make sure its bookmark is visible and located immediately before the first character of the Section Title (see each of the examples further down this page).

​

Do not change the bookmark.

​

The section looks better when on a page with portrait orientation. 

​

 

Test Case Section

​

In a Test Case, the VTS section is optional and can be located anywhere between the Description sections and the Transaction Timer section.

​

It is semi-structured as described above.

​

If you know that a test case won't require VTS rules, you may decide to delete the section. This can be done in two ways:

  1. Using the DoxRunner Manage Sections operation;

  2. Manually.

​

If you deleted the section from the test case and decide to re-add it, then it can be done in two ways also:

  1. Using the DoxRunner Manage Sections operation;

  2. Manually.

​

If the Solution document also contains a VTS section with a Parameter name that is the same as one in a Test Case, then the one in the Test Case takes precedence.

​

The illustration below shows a typical VTS section as it appears in a Test Case. Note the following points:

  • The Bookmark must be structured as shown in the previous section:

    • That is, "P_", followed by the Test Case ID, followed by "_VTS";

    • For example, if the Test Case ID is TC435, then the bookmark should be P_TC435_VTS;

  • The      symbol is an optional link to the top of the Test Case for easier navigation.

​

Example

​

TemplateSection
TestCaseSection.gif

 

Test Case Template Section

​

The VTS section is optional and can be located anywhere in the Test Case Template between the Description sections and the Transaction Timer section.

​

It is semi-structured. The structure is described above.

​

It must be referenced by a Bookmark that must be located immediately before the Section Title.

 

The Bookmark is structured as follows:  P_VTS

​

The Body Text is expected to contain generic text that will be copied to any new Test Case then updated by the scripter.

​

The Table must have a minimum of two rows - a Heading row and a Data row - and two columns as shown below.

 

It is recommended that you leave the table empty and populate it only after it's incorporated into a Test Case. If the Data row contains a rule, then that rule is copied to any new Test Case.

​

Example

​

SolutionSection
TemplateSection.gif

 

Solution Document Section

​

The VTS section is optional and can be located anywhere in the Solution document.

​

VTS rules are normally defined in the VTS section of a Test Case, however they can also be documented in the Solution document.  This is optional. A VTS section is included in the original downloaded version of the Solution document and is available unless it was manually deleted after the document was downloaded.

​

There is only one way to add rules to the VTS section of a Solution document and that is to manually insert them into the table.

​

If it exists, the section it is semi-structured. The structure is described above and is identical to the Test Case.

​

It must be referenced by a Bookmark that must be located immediately before the Section Title. 

 

The Bookmark is structured as follows: V_VTS

​

Why would you use the Solution document to document VTS rules? You don't need to, but if there are rules that are common across multiple test cases, then they may be easier to manage if placed in the Solution document instead. In fact, to take an extreme view, you can document -all- VTS rules in the Solution document and define -none- in the Test Cases, if that is easier to manage. The choice is yours.

​

If a rule in a Data row of the Table contains a Parameter name that is the same as one in a Test Case then the one in the Test Case takes precedence.

​

Example

​

SolutionSection.gif
AddRule

 

Add a VTS rule

​

In all cases, each VTS rule is documented as a row in the table that is embedded in a VTS section. The section must exist in the appropriate place beforehand.

​

They can be added to a Test Case in three ways:

  1. Manually add a row in the table that should exist in the appropriate VTS section;

  2. Via the green Parameter Association screen during a Process Raw operation;

  3. Via the Reverse Engineer operation from a legacy script.

​

They can only be added to the Solution document or the Test Case Template manually. 

 

An empty table is present in the Test Case Template when downloaded from this site. Rules are not normally added to this table, but can be in the rare case where a rule is known to be needed in all (or most) new test cases.

​

AddManually

​

Add a VTS rule manually

 

This can be done in a Test Case, the Solution document, and the Test Case Template. Make sure the VTS section exists. It should exist unless you have deleted it.

​

Adding a rule manually is simply a matter of adding a row to the table and typing in the details, making sure there is one row per parameter as illustrated below. Only the Parameter and Configuration columns are used by the Process Raw operation.

 

Extra columns can be added, but are ignored by the Process Raw operation. A Description column is optional but recommended.

 

Refer to the Overview above for details of each column. Take particular note of the Configuration column.

​

AddViaParameterAssociaion
AddManually.gif

Example

​

 

Add using the Green Parameter Association Screen

​

If, during the Process Raw operation, it is noticed that a VTS rule can be applied to an Unassociated Name / Value Pair (that is, one that appears in the top left hand pane of the green Parameter Association screen), then it can be added to the Test Case.

​

This is done implicitly if you type in new details in the boxes at the bottom of the top right hand pane. Note that the Description isn't added here - it must be added to the rule in the table manually once the Process Raw operation has completed.

​

AddViaReverseEngineer

 

Add using the Reverse Engineer Operation

​

The Reverse Engineer operation is designed to update the documentation for a Test Case from a legacy script.

 

VTS rules are included in this process, however it's possible that not all rules are captured and documented.

 

Make sure you check the Test Case once the Reverse Engineer operation has completed. 

​

DeleteRule

 

Delete a Rule

​

Except for the last rule, deleting one can be done manually in all documents by simply deleting the respective row in the table.

​

Deleting the last rule can be done in two ways:

  • Simply clear all cells in the row (do not delete the row);

  • Delete the entire section.

​

A rule can also be deleted from a Test Case via the green Parameter Association screen during a Process Raw operation, as described below.

​

DeleteViaGreenScreen

 

Delete using the Green Parameter Association Screen

​

If, during the Process Raw operation, a VTS rule is noticed that is no longer required, it can be deleted from the Test Case using the Delete from document button that appears on the green Parameter Association screen.

​

bottom of page