Load Runner Tips::

Load Runner Interview Questions Level 1

Question 1: What is the load testing process in LoadRunner?

Step 1: Planning the test: Involves development of a clearly defined test plan to ensure that the newly developed test scenarios are able to accomplish the load-testing objectives.

Step 2: Creation of Vusers: Involves creation of Vuser scripts which contain various tasks performed by every Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions.

Step 3: Scenario Creation: A scenario describes the events that occur during a test execution. It includes a list of machines(LGs), scripts, and Vusers that run during the scenario. Scenario is created by using LoadRunner Controller. We can prepare manual scenarios as well as goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load generator (LG) machines, and number of Vusers to be assigned to each script. For web tests, we need to create a goal-oriented scenario where we define the goal that our test has to achieve. LR automatically builds a scenario for us.

Step 4: Scenario Run: The load on the server is emulated by configuring multiple Vusers to perform the tasks simultaneously. Before the test run, we set the scenario configuration and scheduling. We can run the either entire scenario or Vuser groups, or individual Vusers.

Step 5: Monitoring the scenario: Scenario execution is monitored 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 etc.

Step 6: Analyzing test results: During scenario execution, LoadRunner records the performance of the application under various loads. LoadRunner's graphs and reports are used to analyze the application's performance.

Question 2: What are the components of LoadRunner?

Following are the components of loadrunner:

Virtual User Generator: It is commonly known as Vugen, it helps in recording the vuser scripts that emulates the action of real users for different types of application and communication protocol.

Controller: The Controller is used to run the script in multi-user mode. It is administrative center for load test scenario creation, maintenance and execution. It assigns scenarios to vusers and LGs, starts and stops the tests. During the execution the Controller receives real-time monitoring data and displays status.

Load Generator:generates the load against the application on which test is being is performed.

Agent Process: It is a part of controller which helps in communication between Load Generators and Controller. Analysis: It assembles logs from various load generators and prepares reports for visualization of run result data and monitoring data.

Question 3: Which Component of LoadRunner is used for recording a Script?

Virtual User Generator: It is commonly known as Vugen, it helps in recording the vuser scripts that emulates the action of real users for different types of application and communication protocol.

Question 4: What is a rendezvous point LoadRunner?

Rendezvous points are inserted into scripts to emulate heavy or peak load on the server.

Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to come at a certain point, in order that they may simultaneously perform a task. For example, to emulate peak load on the flight booking server, you can insert a rendezvous point instructing 200 Vusers to book ticket at the same time. .

Question 5: Which Component of LoadRunner is used to playback the script in multi user mode?

Controller component is used to play the script in multi-user mode. It happens during a scenario run where a vuser script is executed by a number of vusers in a group.

Question 6: What is a scenario in LoadRunner?

A scenario defines the events which occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the LGs on which the virtual users run their emulations.

Question 7: Why parameters are required in LoadRunner?

Parameters are like script variables. It is used to vary input to the server and to emulate real users. Different sets of input data are sent to the server each time the script is run. One script can emulate different users on the system.

Question 8: What is the difference between Ramp up and Ramp Down?

Ramp up is the rate at which virtual users add to the load test .
Ramp Down is the rate at which virtual users exit from the load test.

Question 9: How is Automated Correlation configured???

Any setting related to Automatic Correlation can be performed by General Options->Correlation. Correlation rules are set from Recording options->Correlations

Question 10: How do you identify what to correlate and what to parameterize?

Correlation is required when a value changes in the script on each run or iteration.
Parameterization needs to be done to vary any user input.

Next


	Load Runner Interview Questions Level 1 Question 1: What is the load testing process in LoadRunner? Step 1: Planning the test: Involves development of a clearly defined test plan to ensure that the newly developed test scenarios are able to accomplish the load-testing objectives. Step 2: Creation of Vusers: Involves creation of Vuser scripts which contain various tasks performed by every Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions. Step 3: Scenario Creation: A scenario describes the events that occur during a test execution. It includes a list of machines(LGs), scripts, and Vusers that run during the scenario. Scenario is created by using LoadRunner Controller. We can prepare manual scenarios as well as goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load generator (LG) machines, and number of Vusers to be assigned to each script. For web tests, we need to create a goal-oriented scenario where we define the goal that our test has to achieve. LR automatically builds a scenario for us. Step 4: Scenario Run: The load on the server is emulated by configuring multiple Vusers to perform the tasks simultaneously. Before the test run, we set the scenario configuration and scheduling. We can run the either entire scenario or Vuser groups, or individual Vusers. Step 5: Monitoring the scenario: Scenario execution is monitored 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 etc. Step 6: Analyzing test results: During scenario execution, LoadRunner records the performance of the application under various loads. LoadRunner's graphs and reports are used to analyze the application's performance. Question 2: What are the components of LoadRunner? Following are the components of loadrunner: Virtual User Generator: It is commonly known as Vugen, it helps in recording the vuser scripts that emulates the action of real users for different types of application and communication protocol. Controller: The Controller is used to run the script in multi-user mode. It is administrative center for load test scenario creation, maintenance and execution. It assigns scenarios to vusers and LGs, starts and stops the tests. During the execution the Controller receives real-time monitoring data and displays status. Load Generator:generates the load against the application on which test is being is performed. Agent Process: It is a part of controller which helps in communication between Load Generators and Controller. Analysis: It assembles logs from various load generators and prepares reports for visualization of run result data and monitoring data. Question 3: Which Component of LoadRunner is used for recording a Script? Virtual User Generator: It is commonly known as Vugen, it helps in recording the vuser scripts that emulates the action of real users for different types of application and communication protocol. Question 4: What is a rendezvous point LoadRunner? Rendezvous points are inserted into scripts to emulate heavy or peak load on the server. Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to come at a certain point, in order that they may simultaneously perform a task. For example, to emulate peak load on the flight booking server, you can insert a rendezvous point instructing 200 Vusers to book ticket at the same time. . Question 5: Which Component of LoadRunner is used to playback the script in multi user mode? Controller component is used to play the script in multi-user mode. It happens during a scenario run where a vuser script is executed by a number of vusers in a group. Question 6: What is a scenario in LoadRunner? A scenario defines the events which occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the LGs on which the virtual users run their emulations. Question 7: Why parameters are required in LoadRunner? Parameters are like script variables. It is used to vary input to the server and to emulate real users. Different sets of input data are sent to the server each time the script is run. One script can emulate different users on the system. Question 8: What is the difference between Ramp up and Ramp Down? Ramp up is the rate at which virtual users add to the load test . Ramp Down is the rate at which virtual users exit from the load test. Question 9: How is Automated Correlation configured??? Any setting related to Automatic Correlation can be performed by General Options->Correlation. Correlation rules are set from Recording options->Correlations Question 10: How do you identify what to correlate and what to parameterize? Correlation is required when a value changes in the script on each run or iteration. Parameterization needs to be done to vary any user input. Next
	FIND MORE ON LOAD RUNNER TIPS \| About Load Runner \| Creating scripts in Load Runner \| Load Runner scenario \| LR Analysis \| Performance Tuning \| Performance Testing \| LR Errors \| Interview Question \| Load Runner Tool \| Correlation Practice \| Site Map \|