URL vs. HTML 录制模式

对于WEB协议，LoadRunner支持3种模式的录制：GUI-based、HTML based和URLbased，这篇文章对比了一下URL和HTML模式：

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

 

There are three types of recording mode/levels in LoadRunner. GUI-based, HTML based and URL based. For the uninitiated, recording levels tells you the amount of and what information is recorded during the recording process. As the title says, for this post we will keep focus on HTML based and URL based recording levels only and will touch upon GUI based mode, in a later post.

1. HTML based mode, records script for every user action that is performed during recording (hmmm…sounds like QTP) 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 you inside information like what is happening behind the recording while URL based mode records each and every step and emulate Javascript code.  （HTML模式录制的脚本有点像QTP的脚本，是用户操作层的脚本，而URL模式录制的脚本是针对浏览器和服务器之间的每一个交互进行记录。）
2. From the point1) above you can guess, HTML mode would have less correlation to do while URL mode has much more complex correlation requirements.  （HTML模式的脚本相比起URL模式的脚本，需要的关联处理要少一些。）
3. HTML mode is smaller and is more intuitive to read as the statements are inside the functions corresponding to the user action performed. In the case of URL based, all statements gets recorded into web_url()   （HTML模式录制的脚本要少一些、直观一些，而URL模式录制的脚本都以web_url函数出现，不够直观和简洁。）
4. HTML mode is recommended for browser applications while URL mode is recommended for non-browser applications.   （对于那些基于浏览器的应用程序建议采用HTML模式录制，而对于那些客户端不是基于浏览器与服务器端交互的应用程序，推荐采用URL模式录制。）
5. Lastly, don’t get the impression that I am advocating for HTML mode. URL mode can be of real help when you want to have control over the resources that need to be or need not to be downloaded, since you have each and every statement in-front of you (point 1)   （URL模式的脚本可以更细粒度地控制资源文件是否要下载。）