URL vs. HTML recording mode

Transferred from: http://blog.csdn.net/testing_is_believing/article/details/5274188

In the Web protocol, LoadRunner supports 3 modes of recording: Gui-based, HTML based, and urlbased, which compares URLs and HTML patterns:

http://learnloadrunner.com/introduction/difference-url-vs-html-recording-mode/

There is three types of recording mode/levels in LoadRunner. Gui-based, HTML based and URL based. For the uninitiated, recording levels tells your the amount of and what information is recorded during the recording proces S. As the title says, for this post we'll keep focus on HTML based and URLs based recording levels only and would touch up On the GUI based mode, in a later post.

2. HTML based mode, records script for every user action This is performed during recording (Hmmm...sounds like QTP) C1>while URL based mode records each and every browser request to the server and resources received from the server. Confused? OK, HTML based mode does recording as you perform clicks and doesn ' t give are inside information  Hind the recording while URL based mode records each and every step and emulate Javascript code. (the script recorded in HTML mode is a bit like QTP's script, which is a script for the user's action layer, while the URL pattern recording script is recorded for every interaction between the browser and the server.) ）
4. From the Point1) above you can guess, HTML mode would had less correlation to does while URL mode had much more co  Mplex correlation requirements. (The HTML-mode script requires less association processing than the URL-mode script.) ）
6. HTML mode is smaller and was more intuitive to read as the statements was inside the functions corresponding to the user AC tion performed. In the cases of URL based, all statements get recorded into Web_url () (HTML mode recording script is less, more intuitive, and the URL mode recording script appears in Web_url function, not straight View and simplicity. ）
8. HTML mode is recommended for browser applications While the URL mode is recommended for non-browser applications. (HTML mode recording is recommended for those browser-based applications, and URL pattern recording is recommended for applications where clients are not browser-based and server-side interactive.) ）
10. Lastly, don ' t get the impression that I am advocating for HTML mode. URL mode can be is of real help when you want to has control over the resources that need to be or need not to be downloaded , since you has each and every statement In-front of your (point 1) (the URL pattern script can more granular control whether the resource file is to be downloaded or not.) ）

URL vs. HTML recording mode