LoadRunner

web_reg_save_param_xpath

web_reg_save_param_xpath To record the value of an XML node in the server response, use web_reg_save_param_xpath. Most web services return XML as their response format, making it simple to capture these responses by including the name of the XML element (or “node”) in the query string of the function. Some HTML web requests have embedded XML …

web_reg_save_param_xpath Read More »

web_reg_save_param_regexp

One of the simplest ways to create the correlation logic for managing dynamic values in the script is through the use of regular expressions in LoadRunner. The web_reg_save_param_regex method makes use of regular expression tokens to capture dynamic values in the response. Over web_reg_save_param, the key benefit of web_reg_save_param_regexp is the ability to escape the …

web_reg_save_param_regexp Read More »

web_reg_save_param_ex

web_reg_save_param_ex The ‘web_reg_save_param’ function for the C language version of Micro Focus LoadRunner has been deprecated and replaced by the ‘web_reg_save_param_ex’ method. This is the ‘web_reg_save_param’ function in an expanded format with new significant attributes. By comparing the differences between the two, you can understand why some more features have been eliminated. ‘web_reg_save_param’ and ‘web_reg_save_param_ex’ …

web_reg_save_param_ex Read More »

web_reg_save_param

web_reg_save_param The LoadRunner function “web_reg_save_param” is used to manage the dynamic values returned by the server in the response. The ‘Correlation – Overview’ article has already discussed the fundamental idea of dynamic value. As you continued, you learned about the several types of correlation, including autocorrelation and manual correlation. When you select the ‘Correlate’ button …

web_reg_save_param Read More »

Manual Correlation

Manual LoadRunner mapping As we continue our discussion of mapping, we now come to manual mapping. In my previous blogs, I have covered the basics of correlation and autocorrelation. Manual mapping is a technique for locating dynamic values that require manual work. When using automatic mapping, dynamic values can occasionally be 100% bound (this is …

Manual Correlation Read More »

Automatic Correlation

Automatic Correlation for LoadRunner The automated correlation denotes that, following script generation and replay, after applying some predefined or manually applied conditions before recording, the LoadRunner (VuGen) discovers the dynamic value. You can use the automatic correlation to: R3 (Rule, Record, Replay) can be used as a general guideline for automatic correlation techniques. Let’s go …

Automatic Correlation Read More »

Correlation

LoadRunner  Correlation  overview The term “map” describes how dynamic values received from the server are processed. This dynamic data, such as session ID and authorization token, are the distinguishing values that are generated by the server for security purposes. Dynamic values can also relate to site content, such as dropdown options, dates, item and product …

Correlation Read More »

Script Debugging

Debugging the LoadRunner script VuGen converts user activity into a program called a Vuser script after capturing actual user behavior (business process) on a website. You cannot use the same Vuser script to perform a performance test with LoadRunner because you need to do some basic debugging, such as dynamic value handling and flow verification, …

Script Debugging Read More »

Script Recording

How is a LoadRunner script recorded? You are now prepared to record your first LoadRunner script after learning about the terminology and Basic Scripting Steps. Mercury created the “Recording” option when they first released LoadRunner, which is a simple and time-saving tool. A performance tester can easily explore the website’s pages while using the recording …

Script Recording Read More »

Scroll to Top