Step 1: Planning the test. Here, we develop a clearly
defined test plan to ensure the test scenarios we develop
will accomplish load-testing objectives.

 Step 2: Creating Vusers. Here, we create Vuser scripts that
contain tasks performed by each Vuser, tasks performed by
Vusers as a whole, and tasks measured as transactions.

 Step 3: Creating the scenario. A scenario describes the
events that occur during a testing session. It includes a
list of machines, scripts, and Vusers that run during the
scenario. We create scenarios using LoadRunner Controller.
We can create manual scenarios as well as goal-oriented
scenarios. In manual scenarios, we define the number of
Vusers, the load generator machines, and percentage of
Vusers to be assigned to each script. For web tests, we may
create a goal-oriented scenario where we define the goal
that our test has to achieve. LoadRunner automatically
builds a scenario for us. 

Step 4: Running the scenario.We emulate load on the server
by instructing multiple Vusers to perform tasks
simultaneously. Before the testing, we set the scenario
configuration and scheduling. We can run the entire
scenario, Vuser groups, or individual Vusers.

 Step 5: Monitoring the scenario.We monitor scenario
execution using the LoadRunner online runtime, transaction,
system resource, Web resource, Web server resource, Web
application server resource, database server resource,
network delay, streaming media resource, firewall server
resource, ERP server resource, and Java performance monitors. 

Step 6: Analyzing test results. During scenario execution,
LoadRunner records the performance of the application under
different loads. We use LoadRunner?s graphs and reports to
analyze the application?s performance.