There are three types of recording mode/levels in Load Runner. 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.
HTML based mode, records script for every user action that is performed during recording while URL based mode records each and every browser request to the server and resources received from the server.
HTML based recording:
1.It will capture only HTML based resources.
2.URLs are developed based on each action performed by the
user.
3.Resource=0 for all the URLs generated under HTML based
recording
4.Functions developed under this are
i.web_url
ii.web_link
iii.web_submit_data
iv.web_submit_form
URL based recording:
1.It will capture all the Non-HTML bases resources in the
application i.e, Jpeg,bitmap etc
2.URLs are developed based on the steps performed by the
user.
3.Resource=1 for all the URLs in the developed script.
Note:Resource=0 is also some times being displayed in the
script
4.Functions developed under this are
i.web_url
ii.web_submit_data
iii.web_concurrent_start
iv.web_concurrent_end
HTML based mode, records script for every user action that is performed during recording while URL based mode records each and every browser request to the server and resources received from the server.
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 Java script code.
From the point 1)HTML mode would have less correlation to do while URL mode has much more complex correlation requirements.
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 mode is recommended for browser applications while URL mode is recommended for non-browser applications.
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.
From the point 1)HTML mode would have less correlation to do while URL mode has much more complex correlation requirements.
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 mode is recommended for browser applications while URL mode is recommended for non-browser applications.
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.
some other differences:
HTML based recording:
1.It will capture only HTML based resources.
2.URLs are developed based on each action performed by the
user.
3.Resource=0 for all the URLs generated under HTML based
recording
4.Functions developed under this are
i.web_url
ii.web_link
iii.web_submit_data
iv.web_submit_form
URL based recording:
1.It will capture all the Non-HTML bases resources in the
application i.e, Jpeg,bitmap etc
2.URLs are developed based on the steps performed by the
user.
3.Resource=1 for all the URLs in the developed script.
Note:Resource=0 is also some times being displayed in the
script
4.Functions developed under this are
i.web_url
ii.web_submit_data
iii.web_concurrent_start
iv.web_concurrent_end