Parameterizing Session Data: Introduction

How do I get to the Parameterization screen?

 

Suite Manager >> Continue with Web Performance Testing >> Select load test from left-side tree view >> Click 'Edit' link under HTTP Parameters from the right panel.

 

Understanding Parameterization UI

 

The Parameterization screen displays the following details:  

  1. The left side panel displays the list of URLs for the selected transaction.

  2. The right panel of the Parameterize screen displays the following tabs:

    1. Parameters - Displays the list of parameters passed in get/post data.

    2. Mime - Displays the list of filePath (File upload and download parameters) passed in get/post data.

    3. URL Rewriting - Displays the URL to parameterize the session identifiers.

    4. Store Variables - To fetch values from dataset, text, hidden elements, cookies, javascript or constant and store it in a variable.

    5. Cookies - Displays the list of cookies passed in get/post data.

    6. Header - Displays info such as Client Request and Server Response.

  3. Clicking the URL Rewriting tab displays the selected URL in the URL text area. You can select the session identifiers passed in URL to parameterize the session identifiers (url-rewriting) where you can fetch values from dataset, cookie, text, element, javascript, constant, URL, or variable or Select Complete URL check box to replace the Complete URL with the value fetched from text, element or javascript.

  4. Clicking the Cookies or Parameters or MIME tab displays a table showing the name of the selected cookie or parameter or MIME type in the Name column. The Value column shows the value of the selected cookie or parameter or MIME type or the parameterizated information (if it has been already parameterized). The Fetch Data From column shows the options to parameterize in a list button such as dataset, cookie, text, element, javascript, constant, URL or variable. The Apply to all Urls column displays the checkbox to reuse the configured parameterization for similar cookies or parameters in the selected transaction. To know the details of parameterizing cookies or parameters in get/post data, please refer to the topic Parameterizing Get/Post Data. To know the details of parameterizing MIME types, please refer to the topic Parameterizing MIME Types in Get/Post Data.

Two Ways to Handle Session Data

 

Following are the two ways to handle Session Data:

Replace Complete URL

Replace Session Data Embedded in URL/Path

The description and the steps to configure the various types of parameterization are explained below:

 

Understanding Parameterization Types

 

Supported Parameterization Type

Description

Dataset

When you select the type as dataset, parameterization is done by importing values from Database or FLAT file or XLS file. The detailed steps are explained below.

Cookie

Parameterization is done by substituting the value from the specified Cookie. The detailed steps are explained below.

Text

In this type, Parameterization is done by substituting the value from Text (Response Body of a HTML page). The detailed steps are explained below.

Element

In this type, the value is fetched from the specified element attribute of a HTML page. The detailed steps are explained below.

Javascript

In this type, the value is fetched by executing the specified Javascript. The detailed steps are explained below.

URL

In this type, the value is fetched from the URL of the previous response obtained during playback of the load script. The detailed steps are explained below

Constant Value

This type do not change values between a recorded session and a replay session. The values recorded can be used as it is for replay. The constant value can be specified in the Value field. Click Apply to dynamically substitute the constant value for the selected parameter or cookie.

Variable

In this type, you can fetch values from a dataset, cookie, text, element, javascript, url or a constant and store it in a global variable say in URL1. This variable can then be used in some other URL say URL5 in the same transaction to fetch the value from the variable and substitute it for the session identifier in URL5. The detailed steps are explained below.

Random Data

In this type, you can fetch values from any random data source such as Alphabets, Integers, etc. For more details, refer this link.



Copyright © 1999, AdventNet Inc. All Rights Reserved.