Answer / maheshwar

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

Answer / satish

HTML
Context Sensitive based script recording

HTML-Based / describing user actions is the easiest to maintain

For example, assume there is a link called "Continue" that
sends you to http://localhost/ index.html. Your script
records "Continue", and NOT the destination URL. So, if
sometime later your application developer decides to change
the URL associated with "Continue" to something else - like
http://localhost/ home.html, your script will still work
correctly - and go to "home".

LoadRunner parses the HTML it received from prior server
responses to determine what the full URL is behind the
Continue link(i.e. Context Senistive).

LoadRunner does as much work for you as it can, leaving you
with the fewest script statements to maintain.



URL:
No context would be considered during script recording,
every statement get recorded independently

Every thing would get recorded as URL only. i.e. web_url

In this case if URL based recording is used then script will
fail during replay.

URL mode records every URL that LoadRunner is supposed to
ask for –but without the actual parsing.

So, if a URL is there, LoadRunner simply calls it but does
not examine it for embedded URLs.

This allows(i.e. Not parsing embedded URLs) would make LR to
run very FAST.

But this type of script would become obsolete and you may
not even know it if some thing changes in the application
hence this is very much useful for a stable

Answer / ravikumar.p

Its always a best choice to go for HTML mode.

Url based scripting generates lengthy script and too many
dynamic values when compared to HTML mode

Answer / hariprasad reddy

HTML:-Using this recording mode LR can generate script by
performing certain user actions on only HTML context. This
mode recogneze the user inputs either in the form of data
or in the form of forms.For each action that we perform on
the application, LR generates a function called Web_url.
Along with this 4 more functions will generated (i.e)
depending on actions we perform.These are

web_submit_data
web_submit_form
web_link
web_image

Generally URl based recording mode will be used on Non-HTML
resources like Bitmap,Jpeg,gif..., In this mode LR
generates the function web_url for each and every step that
we perform on the application. this mode recognize the
user input data only in the form of data submitted
function. some more functions will generates such as

web_submit_data
web_concurrent_start
web_concurrent_end

Answer / sujay

In HTML based mode, teh recording of script happens for
every user action that is performed during recording while

URL based mode records every browser request to the server
and resources received from the server.

In HTML mode you will miss quite a bit of Correlation which
may cause issues with replay during the load test

Answer / arun kumar

HTML: Generate a seperated step for each user action. In
addition, for requests whose origin is not basic HTML,
record exolicit requests.

URL: Records all requests & resources from the server. Use
this mode to simulate the former URL based mode with all
resources recorded.

Answer / sulabh jain

please correct if i am wrong.

HTML based recording records only the user actions
where as URL based recording records the requests and
resources for the server.

Answer / akshaya

HTML level will generate a web_submit_form statement that
only records options an end user is allowed to see and
change.

URL level will generate a web_submit_data statement that
records all data that was actually sent from the browser to
the server.

Note:URL mode includes hidden information that the HTML
recording doesnot pick up.Quite often this will include
session ID information.

Answer / surendra

HTML Based script :
~The script describing user actions only.
~In this each user action recorded as a separate request.
~It is a page level(UI level) recording script.
~It is a context sensitive recorded script.
~In this script URL's recorder as web_url(),Links Recorded as web_link(),images Recorded as web_image(),Form Submissions recorded as web_submit_form().
~the size is small(less lines), less customization required, less chances to get dynamic values.
~Maintenance cost is high (Rework require if Ui Changes).

URL Based Script :
~URL based script recording each resources (Html and Non Html in the page) as a separate script.
~it is a network level recorded script.
~it is a context less sensitive recorded script.
~in this Url's,links,images recorded as a web_url(),form submissions recorded as a web_submit_data().
~Size is large (More lines).
~More customization required(Chances to get more dynamic values).
~Script Maintenance cost is low( rework is not require when UI changes happen).

Answer / shaswat

HTML(Context Sensitive)

is usually preferred for several reasons. One of the
reasons is because it is "context sensitive" , i.e.each
mouse click

recorded in the script is made in the context of the
previous step/page. In order to maintain context it looks
through the

previous page to make sure the current operation is
available. This adds extra overhead because it is
performed by a

background utility called the runtime parser. Although
the parser uses extra overhead, it does saves us work in

correlation and page checks. This because if a link/request
is not available, the runtime parser will see that and
throw

an error telling us that the request is not there. (The
old "Requested Form Not Found" error). URL mode, on the
other

hand does not check the context of the previous request.
It will simply make each recorded request individually
regardless

of whether the request is still available on the page or
logically follows in context. That's why URL mode requires
more in

the way of page checks and correlation.

What is scenario default?

0 Answers  

Which is the best institution to learn load runner in Hyderabad?

4 Answers  

Which are online monitors and windows resource monitors

0 Answers   Cap Gemini,

)What r pre settings while recording a script?

2 Answers   EDS,

How can we handle the vUsers with Secure certification.

0 Answers  

The response time of an application was 2.5 seconds.After a minor hotfix,the response time increased to 5 seconds.What analysis can you make out. What are all the things u check in the server side in such a scenario?

4 Answers   Symphony,

What is the function for capturing the streaming vedio (could be a flashplayer) in an web application using Load Runner..?

1 Answers   Capita,

How to write Web_custom_request?

1 Answers   Fidelity,

How should you call loadrunner scripts using testdirector

1 Answers   AZTEC,

When a scenario run exactly what happened?

0 Answers  

what is is difference between load testing and other testings?

1 Answers   4soft solutions, Four soft,

what is sitescope where we can use this?wat is the purpose of this

7 Answers