LoadRunner HTTP/HTML 与 Click&Script
Web(HTTP/HTML):Emulation of communication between a browser and Web Server.
Web(Click and scrīpt):Emulation of the communication between a web browser and the web server at user-action level.
LoadRunner Click&Script 相关介绍：
http://www.sqa.its.state.nc.us/library/pdf/HP%20LoadRunner%20Click%20&%20Script.pdf
Sixty percent of Mercury LoadRunner users test web-based applications. These users typically spend 70 percent of their time scripting tests.
Until now, all scripts were recorded using low-level HTTP protocol to capture web applications for performance testing. But HTTP scripts are long,
time-consuming to create, and hard to interpret and maintain. The most time-consuming task with HTTP-level scripts is correlations — capturing
values that are created in one step (e.g., session ID) and used in another. In some cases, such values cannot be captured, as they are computed by complex client-side JavaScript code, which has to be rewritten in C within the HTTP-level script.
Now, with Mercury LoadRunner Click and Script Technology, users can record scripts at a higher presentation layer, making the scripting process
much easier. Click and Script Technology automatically captures the most valuable scripting information to create intuitive and self-explanatory
scripts, expressed in user-actions terms, such as pressing a button, filling an edit field, etc. It also executes client-side JavaScript code, just like
the browser does, which virtually eliminates the need for correlations. Therefore, it dramatically reduces scripting time and provides much more
succinct information that is easier to interpret and understand. These scripts are also much easier to maintain — since anyone can look at the
scripts and quickly see what is going on in each statement.
LoadRunner Click&script 录制Tips：
Use the mouse and not the keyboard
It is preferable to click on an object with the mouse rather then using the keyboard. During recording, use only GUI objects that are within the browser's pane. Do not use any browser icons, controls, the Stop button, or menu items, such as View > Refresh. You may, however, use the Refresh, Home, Back and Forward buttons and the address bar.
Do not record over an existing script
It is best to record into a newly created script—not an existing one.
Avoid context menus
Avoid using context menus during recording. Context menus are menus which pop up when clicking an item in a graphical user interface, such as right-click menus.
Avoid working in another browser while recording
During recording, do not work in any browser window other than the browser windows opened by VuGen.
Wait for downloads
Wait for all downloads to complete before doing any action, such as clicking on a button or filling in a text field.
Wait for pages to load
During recording, it is best to wait for the page to load completely before doing the next step. If you did not wait for all of the pages to load, record the script again.
Navigate to start page
If the last page in an action does not contain the links and buttons that were available at the start of the iteration, then the next iteration will fail. For example, if the first page has a text link Book A Flight, make sure to navigate to the appropriate page at the end of your recording, so that the same link will be visible at the end of the business process.
Use a higher event configuration level
Record the business process again the High Event Configuration level. For more information on changing the Event Configuration level, see "Dynamic menu navigation was not recorded" on page 556.
Disable socket level recording
In certain cases, the capturing of the socket level messages disrupts the application. For most recordings, socket level data is not required. To prevent the recording of socket level data, disable the option in the recording options. For more information, see the section about recording
with Click and Script.
Enable the record rendering-related property values
If the client-side scripts of the application use a lot of styling activities, enable the Record rendering-related property values option before recording the script. For example, enable this option to record additional DOM properties such as offsetTop. Note that enabling this option may
decrease the recording speed. You can enable the Recording Options > GUI Properties > Advanced node.