LoadRunner - Web (HTTP/ HTML) Vs Web (Click and Script)

When the Web Vuser script is created there are two options to choose Web (HTTP/ HTML) and Web (Click and Script). The testers always have the confusion, when to use Web (HTTP/ HTML) and Web (Click and Script).

Though many of the users use Web (HTTP/ HTML) as default mode of recording. Let us see how and which of the scenrios Web (Click and Script) will be useful.


Web (Click and Script) Vuser Web (HTTP/ HTML) Vuser
Emulation of communication between Browser and Web Server at user action level Emulation of communication between Browser and Web Server.
The events will be captured at the browser page GUI elements level The events will be captured at the HTTP Protocol level on a specific browser
The scripts contain detailed information about the GUI events The scripts contain detailed information about the recorded traffic.
Some of the common functions generated on different GUI objects are:
• web_browser (for invoking the URL)
• web_edit_field (to set the value to a edit box)
• web_image_submit (to click on a image button, which will send the data to the server)
• web_image_link (to click on a image link)
• web_list ( to select an item from a list)
• web_check_box (to set on or off on a check box)
• web_radio_group (to select an item from a radio group)
Some of the common functions generated at HTML based script
• web_url (Loads the specified Web page)
• web_submit_data (Performs an "unconditional" or "contextless" form submission)
• web_reg_save_param (Registers a request to save dynamic data information to a parameter)
Support non-HTML code such as Javascript on the client side. Do not support Applets or VB Script As Web (HTTP/ HTML) records at the protocol level, it doesn’t have any client side scripting dependency. So, it supports all client side scripts
Accurately emulates user actions on the Web page (the way the user does step by step) and executes the necessary Javascript code Emulates the page submissions and HTTP traffic. Doesn’t emulate user actions as you do step by step on the GUI pages.
For each user step on the GUI, an event or function will be captured on the Vuser script For each page submission or server request an event or function will be generated
Most of the dynamic data (sessions, cookies, etc.) handled automatically. The reason, the script events are captured at the GUI level. Normally the session or cookie related issues will come when the complete page data is submitted on the server All the dynamic data needs to be handled by way of correlations
Provides three levels of recording:
• GUI Based script,
• HTML-based script
• and URL-based script
Provides Two levels of recording:
• HTML-based script
• and URL-based script
For most applications, including those with JavaScript, use Web (Click and Script) Vusers For browser applications with applets and VB Script or for non-browser applications, use the Web (HTTP/HTML) Vuser.
Allows user to generate detailed (event specific) Business Process Reports which summarize the script. Allows user to generate page specific Business Process Reports which summarize the script.