LoadRunner Correlation – Overview

‘Correlation’ term refers to the handling of dynamic values coming from the server. These dynamic values are the unique values that are generated by the server for security purposes like the session ID, authorization token etc. In some cases, dynamic values also refer to the web content like values in a drop-down list, calendar date, item ID, product ID, order number etc. Through correlation, you can capture these dynamic values and pass them in the subsequent requests. This is the basic concept of ‘Correlation’ in LoadRunner.

Why do we need to correlate the dynamic values?

To get the answer to this question, firstly you need to understand what exactly happens at the time of script recording, script replay and after correlating the dynamic values.

Let’s see, how the client and server act when some dynamic values are exchanged between them.┬áThis is the scenario while you record a script:

Figure 01: Recording Scenario

When you replay the script without any changes then the script fails because of the dynamic value (sessionid) generated by the server does not match the value returned by the client. Refer to the given Figure 02, while replaying the script, the server generated the session id as 222, but vuser script sent the recorded value i.e. 111 which was captured during recording (Figure 01). Hence the server refused to serve the request and threw an error.

Figure 02: Replay without correlation Scenario

Now, when you correlate the dynamic value (sessionid) and replay the script then the vuser script captures and saves the latest value generated by the server and sends it back to the server in the next request. The server validates the returned value with the generated value and gives the proper response. Hence the request is marked as passed at the user end.

Figure 03

Hope you understood, why correlation is so important in VuGen scripting.

Now, the second thing that you should know is:

What are the common values that require correlation?

  1. Session ID
  2. Access Token
  3. Customer Name / ID
  4. Order Number
  5. Bill Number
  6. Number of records displayed on a page
  7. Current Date and Time

There could be more values that depend on the type of application and the term used to denote them. Keep in mind your ultimate goal must be to find out all the dynamic values that cause the failure of the script and correlate them. Now, the next question arises “HOW?”

In LoadRunner, there are two methods to correlate the dynamic values which are:

  1. Automatic Correlation
  2. Manual Correlation

If we further categorise automatic and manual correlation then we can see there are multiple methods to find out the dynamic values in the script. Those methods are:

1. Automatic Correlation

  1. before recording (Rules)
  2. after recording (Record)
  3. after replay (Replay)

2. Manual Correlation

  1. Using WDiff (By comparing two scripts for identical flow)
  2. Using Replay Log

This is an overview of the correlation topic which also covers the requirement of correlation in Performance Testing. The next posts will cover detailed information on Automatic and Manual Correlation.


You may be interested:


Leave a Comment