what is the difference between the HTML and URL based
recording in load Runner?
- 14 Answers
- 69067 Views
- TCS, I also Faced
- E-Mail Answers
Answer Posted / 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
| Is This Answer Correct ? | 20 Yes | 5 No |
Post New Answer View All Answers
What is parameterization?
What are the challenges that you will face to script the step “select all” and then “delete” for any mail account?
How will you stop the execution of a script on error?
How load runner interacts with the application?
What are the 5 icons appear in the buttom of the controller windows?
What are the different sections of the script? In what sequence do these sections run?
Which components have you used in loadrunner ?
What are the information crating for each host?
What is extended log?
How many users can I emulate with loadrunner on a pc?
You want to have each step in your script measured as a transaction in the controller and not shown in the replay log in vugen. How can you accomplish this?
What is the loadrunner start-transaction and its syntax?
What is the number of graphs you can monitor using controller at a time? What is the max of them?
what is remote performance monitering?
How can we find database related issues?
