The automatic correlation (correlation) of loadrunner11 fails.

According to the LoadRunner official document tutorial test "solving common playback problems", the problems encountered are summarized as follows.

Problems:

1. LoadRunner cannot find the dynamic value after recording and playback, that is, the difference between two logs.

2. After Association, the video cannot be played back successfully.

Solution:

Before recording, select the LoadRunner working directory, that is, the bin directory under the installation directory.

 

When you need to verify the user session ID, the recorded script will no longer be able to replay, because the two session IDs are inconsistent. This session ID is dynamically changed. You need to record it to a variable and use the new value each time. Otherwise, the old value relpay will fail. As follows:

 

After the failure, click "show and resolve dynamic server value" on the "verify replay" interface to compare the differences between the recording and the replaying log, that is, the detected dynamic server value. Check and check. The difference is the user session ID (sometimes, although the log is different, it can be ignored, such as thinking time ).

After this option is selected, click "correlation" to automatically associate it.

After Association, open the Script View and view the web_reg_save_param_ex function.

The dynamic values between lb and rbare saved to correlationparameter_1.

However, if we find that the user session ID cannot be the same if it is saved Based on the automatically associated left and right boundaries, this only means that the user session ID is the same.

Therefore, you need to modify it as follows:

In this way, the values in the user session ID can be dynamically saved.

However, the script is replayed and still fails.

Check the script and find the web_submit_data function, as shown below:

In value, the boundaries replaced by correlationparameter_1 are still automatically generated by the machine. Therefore, only this part is replaced at each replacement. Modify it as follows:

Play back again. The user session ID can be dynamically replaced and implemented successfully.

 

The automatic correlation (correlation) of loadrunner11 fails.