Working with LoadRunner

Suppose you want to test a bank server that serves many automatic teller machines (ATMs).

The ATMs provide a full range of banking services to the bank’s customers–such as withdrawing and depositing cash. To test the bank server using LoadRunner, you create a scenario. The scenario defines the actions that are performed on the server during the load test. During the scenario that loads and monitors the bank server, you want to:

• emulate conditions of controlled load on the server

• emulate conditions of maximum load on the server

• measure server performance under load

• check where performance delays occur: network or client delays, CPU performance, I/O
delays, database locking, or other issues at the server monitor the network and server
resources under load

Points to note with web_url and web_link:

• web_url is not a context sensitive function while web_link is a context sensitive function. Context
sensitive functions describe your actions in terms of GUI objects (such as windows, lists, and
buttons). Check HTML vs URL recording mode.

• If web_url statement occurs before a context sensitive statement like web_link, it should hit the
server, otherwise your script will get error’ed out.

• While recording, if you switch between the actions, the first statement recorded in a given action
will never be a context sensitive statement.

• The first argument of a web_link, web_url, web_image or in general web_* does not affect the
script replay. For example: if your web_link statements were recorded as web_link(”Hi There”,

“Text=Hello, ABC”,

LAST);

Now, when you parameterize/correlate the first argument to
web_link(”{Welcome to LearnLoadRunner}”,

“Text=Hello, ABC”,

LAST);

On executing the above script you won’t find the actual text of the parameter {Welcome to Learn LoadRunner} instead you will find {Welcome to Learn LoadRunner} itself in the execution log. However to show the correlated/parameterized data you can use lr_eval_string to evaluate the parameter.