top of page

Overview

​

xxx

​

Overview

Parameter

​

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

​

It must also conform to LoadRunner rules.

​

Parameter

Role

​

Role

Configuration

​

Configuraion

 

Section Management - REGEX Correlation Rules

​

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

​

Each instance of the REGEX Correlation Rule section consists of:

  • a Section Title;

  • a Bookmark;

  • free-form Body Text;

  • a Table with a minimum of three columns (Parameter, Role 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 three columns:

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

​

SectionManagment
Advice
Common Characteristics
TestCaseSection

​

Advice

​

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

  1. Whether the Test Case needs REGEX Correlation rules;

  2. 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, Role, 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 Regex Correlation Rules 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 Regex Correlation 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 Regex Correlation Rules section with a rule 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 Text Data File 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 "_RegexCorrelation";

    • For example, if the Test Case ID is TC534, then the bookmark should be P_TC534_RegexCorrelation;

  • The      symbol is an optional link to the top of the test case for easier navigation.

​

Example

​

 

Test Case Template Section

​

The Regex Correlation Rules 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_RegexCorrelation

​

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.

​

TemplateSection

Example

​

SolutionSection

 

Solution Document Section

​

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

​

Regex Correlation rules are normally defined in the Regex Correlation section of a test case, however they can also be documented in the Solution document.  This is optional. One 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 Regex Correlation 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_RegexCorrelation

​

Why would you use the Solution document to document Regex Correlation 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- Regex Correlation 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 rule that is the same as one in a test case then the one in the test case takes precedence.

​

Example

​

AddRule

 

Add a Regex rule

​

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

​

They can be added to a test case in two ways:

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

  2. 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 Regex rule manually

 

This can be done in a test case, the Solution document, and the Test Case Template. Make sure the Regex 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 at least one row containing a Role of Request and one for Response for each Parameter as illustrated below. Only the Parameter, Role, and Configuration columns are used by the Process Raw operation. There can be more than one Request and more than one Response per Parameter name.

 

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.

​

 

Add using the Reverse Engineer Operation

​

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

 

xxx 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. 

​

AddViaReverseEngineer

 

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.

​

DeleteRule
bottom of page