Common terms used in LoadRunner
Scenarios: Scenarios define the events that occur during each testing session. In LoadRunner, we can divide the performance testing requirements into multiple scenarios. Basically, a scenario defines and controls:
- Number of Vusers to emulate
- Actions that they perform
- Machines on which they run
Vusers: Vuser as the name implies – Virtual User. LoadRunner replaces human users with Vusers. During a scenario run, Vusers emulate the actions of human users to the server and the application. A scenario can contain multiple Vusers like tens, hundreds, or even thousands.
Vuser Scripts: Vuser scripts describe the actions to be performed by Vuser during the scenario run. During a scenario run, Vuser execute Vuser script which include functions to measure the performance of the server during that particular scenario.
Transactions: Transactions are defined in the Vuser script to measure the performance of the server. These are defined to capture the response time taken by the server for the task.
Rendezvous Points: Rendezvous points instruct multiple Vusers to perform a task or set of tasks at the same time to emulate a heavy user load on the server.
Controller: Controller is used to manage and maintain the scenarios from a single workstation.
Hosts: Host is a machine used to execute the vuser scripts. It enables the vusers to emulate the actions similar to a human user. At the time of scenario execution, the LoadRunner Controller distribute Vusers in the scenario to hosts.
Performance Analysis: A Vuser script includes functions that measure the system performance during load testing sessions. Network and server resources can be monitored during the scenario run. After the successful run of a scenario, performance analysis data can be viewed in reports and graphs.