There are five steps in LoadRunner Testing Process:

Successful load testing requires that you develop a thorough test plan. A clearly defined test plan will ensure that the LoadRunner scenarios that you develop will accomplish your load testing objectives.

Vusers emulate human users interacting with your client/server system. A Vuser script contains the actions that each virtual user performs during scenario execution.

In each Vuser script you determine the tasks that will be:

• performed by each Vuser


• performed simultaneously by multiple Vusers


• measured as transactions

A scenario describes the events that occur during a client/server testing session. A scenario includes a list of machines that "host" Vusers; a list of Vuser scripts that the Vusers run; and a list of Vusers that run during the scenario. You create scenarios using the LoadRunner Controller.

Creating the List of Hosts to Run Vusers

For each scenario, you create a list of hosts--machines configured to execute Vuser scripts.

For each scenario, you create a list of scripts that Vusers run during scenario execution.

To each Vuser in a scenario, you assign a Vuser script and a host to run the script.

You emulate user load on the server by instructing multiple Vusers to perform tasks simultaneously. You can set the level of load by increasing and decreasing the number of Vusers that perform tasks at the same time.

Before you run a scenario, you set the scenario configuration. This determines how all the hosts and Vusers behave when you run the scenario.

For each scenario, you create a list of scripts that Vusers run during scenario execution.

You can run the entire scenario, individual Vusers, or groups of Vusers (Vuser Groups). While a scenario runs, LoadRunner measures and records the transactions that you defined in each Vuser script.

During scenario execution, LoadRunner records the performance of the client/server system under different loads. You use LoadRunner's graphs and reports to analyze the server's performance.

file:///C:%5CDOCUME%7E1%5COwner%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_editdata.mso -