You are on page 1of 7


Load Runner: Features of Load Runner: Product: Mercury Interactive or Hewlett Packard(HP) Purpose: Performance Testing Tool Kinds of application: All kinds of application (web Based and Window Based). Language:Test Script Language Architecture: Client Server Architecture Components of Load Runner: …………….. 1.vugen 2.Controller 3.Results and Analysis Vugen: The Virtual User Generator, also known as VuGen, is the primary tool for developing Vuser scripts. VuGen not only records Vuser scripts, but also runs them. Running scripts from VuGen is useful for debugging. It enables you to emulate how a Vuser script will run when executed as part of a larger test.

. the Vuser is initialized (loaded) the Vuser is in "Running" status the Vuser finishes or is stopped Controller: It takes the script we generated using vugen and run them through a schedule that we set up.. Design : We can do the Following actions in the design part of the controller  Define the Group Name.Vuser Script Section Script Section vuser_init Actions vuser_end Used when recording.. Load Generator machine(s). and Script(s) for the Vuser group  Add one or more load generator machines to the Vuser group and configure the load generator(s)  Add and configure one or more scripts to the Vuser group  Enable or disable a Vuser group for the scenario  Remove a Vuser group from the scenario  Schedule the Vuser group/scenario  Run the scenario  Stop the scenario  Reset the scenario  Configure scenario result settings Run : . Vuser Quantity..when to activated how to make them as a task group. a login to a server client activity a logoff procedure Is executed when.We scheduled for how many Vusers are activated.

or is transferring files to the load generator The Vuser is being initialized on the remote machine. The script passed.we can do the Following actions in the Run part of the controller     Run the scenario Stop the scenario Reset the scenario Configure scenario result settings Vuser Status Status Down Pending The Vuser is down. The Vuser stopped when the Stop command was invoked. The Vuser is completing the iteration or action it is running before exiting. The Vuser is ready to be initialized and is waiting for an available load generator. A problem occurred with the Vuser. The Vuser has finished running. The Vuser script is being executed on a load generator. Passed Done. The script failed. Failed Error Gradual Exiting Exiting Stopped . The Vuser already performed the init section of the script and is ready to run. The Vuser has arrived at the rendezvous and is waiting to be released by LoadRunner. The Vuser is running. The Vuser has finished running or has been stopped. Description Initializing Ready Running Rendezvous Done. and is now exiting. The Vuser has finished running.

HTTP Responses per Second. Hits per Second Graph The Hits Per Second graph shows the number of hits (HTTP requests) to the Web server (y-axis) as a function of the elapsed time in the scenario or session step (x-axis).Results and Analysis: It allows as to summarise the data. stopped. Hits Per Second. for each transaction. Transactions per Second Graph The Transactions per Second graph displays. Throughput Graph The Throughput graph shows the amount of throughput on the Web server (y-axis) during each second of the scenario or session step run (x-axis). the number of times it passed. passed. Throughput is measured in bytes and .as well as detail of the load test for pinpointing the problems or bottlenecks Transaction Summary Graph The Transaction Summary graph summarizes the number of transactions in the scenario or session step that failed. and ended in error. Summary Reports The Summary report lists statistics about the scenario or session step run and provides links to the following graphs: Running Vusers. and Average Transaction Response Time. Transaction Summary. and stopped during each second of a scenario or session step run. Throughput. failed. Running Vusers Graph The Running Vusers graph displays the number of Vusers that executed Vuser scripts and their status during each second of the test. This graph is useful for determining the Vuser load on your server at any given moment.

Correlation: Correlation allows you to save dynamic values during test execution. Rendezvous Graph The Rendezvous graph indicates when Vusers were released from rendezvous points. it waits until all Vusers participating in the rendezvous arrive.represents the amount of data that the Vusers received from the server at any given second. and the lr_end_transaction function after the transaction Scheduler: . Rendezvous points Rendezvous points to cause multiple Vusers to perform tasks at exactly the same time. lr_rendezvous("rendezvous1"). and how many Vusers were released at each point. thereby creating intense user load on the server. When a Vuser arrives at the rendezvous point. To indicate a transaction to be analyzed. To indicate a transaction to be analyzed. the Vusers are released. When the designated number of Vusers arrive. These settings let you configure the extent of automatic correlation performed by VuGen while recording. Start Transaction: The lr_start_transaction function marks the beginning of a transaction. use the lr_start_transaction and lr_end_transaction functions End Transaction: The lr_end_transaction function marks the end of a transaction and records the amount of time it took to perform the transaction. This graph helps you understand transaction performance times. place the lr_start_transaction function before the transaction.

or starting all the Vusers simultaneously when the test starts. you can set the time at which the scenario will begin running. for a manual scenario. In addition. you can control the execution of your scenario by: • • • limiting the scenario duration gradually running Vusers within a scenario gradually stopping Vusers within a scenario Scheduling Vuser Groups After you create a Vuser group. you can set the duration time of the scenario or of the Vuser groups within the scenario Ramp up: This allows you to choose between gradually adding Vusers to the running test. you can schedule the group's script execution by setting: the amount of time after the start of the scenario that the group must wait before it starts running • the number of Vusers that will run within a specified period of time • the number of Vusers that will be stopped within a specified period of time • the amount of time the group will run • . and stopping them all simultaneously Scheduling a Scenario Using the Schedule Builder.After you create a scenario. Ramp Down: This allows you to choose between gradually stopping Vusers that are running.