In this article, we’ve covered the 25 most frequently asked LoadRunner interview questions and answers.
The reason we picked this topic is because the performance of a web application is critical for its business. And the stakeholders would use all means to improve it.
Quick Introduction to LoadRunner
It is one of the best performance testing tools that many large organizations use. To measure the performance of any web application, there are many performance monitoring solutions available in the market.
LoadRunner is the leader among them, so most IT companies prefer it. Also, being a QA engineer, performance testing is the area where a tester can expect huge growth. That’s why we’ve compiled the list of LoadRunner interview questions to help in clearing the performance testing interview.
For ease, we’ve split the LoadRunner interview questions between two parts. The first part will provide theoretical knowledge about the LoadRunner. And in the second one, you’ll get to learn the basics of configuration and usage of the application.
Why use LoadRunner?
- It is one of the best and certified performance testing tools in the industry.
- It is compatible with most of the upcoming technologies because of the wide range of supported protocols.
Before we begin, please go through the three important prerequisites mentioned below.
It is because merely reading through the list of LoadRunner interview questions wouldn’t help, you should know about its configuration too.
- You must know the exact version of LoadRunner that you are working with.
- If you’ve work experience with an earlier version, keep yourself updated with the features of the newer versions.
- Sometimes you may have to write a script during an interview. So get prepared for the same.
Dear testers just for your information, we have recently published top questions and answers articles related to manual QA and Selenium testing interviews. If any of you are interested, then please go through the below links.
Let’s now dive in and explore the top 25 LoadRunner interview questions and answers.
Top 25 LoadRunner interview questions and answers.
Question-1. What are the different types of Performance testing?
Performance testing certifies the performance of any web application under load and stress conditions. Usually, we measure the system performance in terms of its response time for the user activity.
At the onset, start it in the standalone mode and then do it in a multi-user environment, also observe the effect of multiple transactions vs. single transactions.
Types of Performance Testing.
To test if an application works fine with the loads that result from a large number of simultaneous users and transactions.
To examine application behavior under peak usage periods.
To measure the overall capacity and to determine when the response time turns unacceptable.
Question-2. What are the notable testing solutions for performance testing?
Following are some notable commercial testing tools used widely in the testing sphere.
It’s meant for the Web and other applications. It can operate in a variety of application environments, platforms, and databases. It can employ a number of server monitors to evaluate the performance measurement of each component and tracking of bottlenecks.
2.2. QAload(Compuware).It’s mainly used for load testing of Web, database, and char-based systems.
It allows for comparing the running tests vs. test metrics.
2.4. Rational Performance Tester (IBM).
It specializes in identifying the presence and cause of system performance bottlenecks.
2.5. Silk Performer (Borland).
It can predict the ideal behavior of an e-business environment before being deployed, regardless of the size and complexity.
Question-3. What is a load runner and what types of testing it can perform?
Load Runner is a performance testing tool from HP. This tool supports all aspects such as Load, Stress, Endurance, data volume, and spike Testing.
Question-4. What are the main components of Load Runner?
Load Runner contains the following components.
4.1. Virtual User Generator. It captures end-user business processes and creates an automated performance testing script, known as the Vuser script.
Organizes, drives, manages, and monitors the load test.
4.3. Load generators.
Creates the load by running Vusers.
Helps to view, dissect, and compare the performance results.
Provides a single point of access for all of the LoadRunner components.
Question-5. What are Vusers and Vuser scripts?
Virtual users imitate a human using the application. And perform actions on the application just like a human would have done. When workstations allow only one single human user to work, many Vusers can concurrently work on a single workstation.
5.2. Vuser Scripts.
It is the script that keeps all the actions performed by the Vuser to complete the specific task. Each Vuser invokes a Vuser script when we run a scenario. Vuser script also defines a function to track the performance of the application.
Question-6. How does LoadRunner execute a performance scenario?
You can easily create and run the load test scenario. The following steps are involved in the process.
6.1. Test planning.
A thorough test plan is required for successful load testing.
6.2. Prepare Vuser Script.
The script contains tasks performed by each Vuser or multiple Vuser.
6.3. Define the Scenario.
A scenario describes an event that occurs during a testing session. It includes a list of machines where the Vuser’ will run, a list of scripts to launch by Vuser, and the number of Vusers.
6.4. Run the Scenario.
Emulate load on the server by introducing multiple Vusers to perform the task.
6.5. Monitor performance.
Using LR online run-time, transaction resources, database resources, and firewall resources can be monitored.
6.6. Analyze results.
It produces graphs and reports. You can use them to analyze the performance of an application.
Question-7. Which LoadRunner Component does the recording of the performance test scenario?
The Virtual User Generator (VuGen) component allows the recording of a script. It enables to definition of Vuser scripts for a variety of application types and communication protocols.
Question-8. Define the rendezvous point with an example.
Rendezvous points are used to emulate heavy user load on the server. They instruct Vusers to wait during test execution to enable multitasking.
For example, in an e-commerce application, rendezvous points are added for 1000+ users to bid for a product simultaneously.
Question-9. What is the size of the VUsers required for load testing?
The size of VUsers for load testing depends on the following parameters.
9.1. System under test (SUT),
9.2. Network configurations,
9.3. Hardware settings,
9.4. Available memory, and
9.5. Operating system.
Hence there cannot be any generic value for Vuser.
Question-10. What is the advantage of running Vuser as a process rather than a thread?
When Vuser is run as a process, the copy of the driver program is loaded into memory for each request. This requires a large amount of memory and limits the number of Vusers on a single generator. While Vuser is run as a thread,
While Vuser is run as a thread, the single instance of the driver program facilitates multiple Vusers. You can run more numbers of Vusers on a single generator in the multi-threaded mode.
Question-11. What constitutes a performance test scenario?
A scenario is a sequence of events, or situations, based on certain assumptions and factors (variables) chosen by its creator. For example, a scenario defines-
11.1. The no. of users.
11.2. Action to be performed.
11.3. Virtual machines system.
Question-12. Define throughput and how it relates to response time.
Throughput refers to the number of transactions produced over time during a test. It’s also expressed as the amount of capacity that a website or application can handle.
When we compare it with response time, we will notice both of them decrease simultaneously. Similarly, the peak throughput and highest response time strike approximately at the same time.
Question-13. What is the purpose of an extended log?
An extended log is expected to convey the following information.
13.1. Data returned by the server and any of the advanced traces if available.
13.2. Parameter substitution.
13.3. Other information depends on the options you select in LoadRunner settings.
Question-14. What are the different types of
vUser logs and state the differences?
There are two kinds of vUser logs in LoadRunner, the standard and extended logs. The standard log redirects a subset of functions and messages to the output log. The subset of functions depends on the Vuser type.
However, the extended log captures detailed execution messages into the output log. It is mostly used when the user needs some debug information about parameter substitution.
Question-15. What is the need for Checkpoints in LoadRunner?
While running a test, sometimes we need to check if the desired content is found on the result page. A content check confirms that expected information appears on the Web page.
Two types of content checks are available in LoadRunner.
15.1. Text Check.
Confirm that a text string appears on a web page.
15.2. Image Checks.
Verify an image renders on a web page.
Question-16. How do you define think time in LoadRunner?
Think time corresponds to the user delay between two subsequent requests.
For example, a user opens page 1 and starts filling in the data on page 1. Assume the user took 10 sec to fill in the data.
After that, he submitted page 1, and page 2 was loaded. In this case, the user has waited for 10 seconds between page 1 and page 2. Hence the think time here is 10 sec.
Question-17. What are the types of Goals in the Goal-Oriented Scenario of Load Runner?
Load Runner comes with five different types of goals.
17.1. The number of concurrent
17.2. The number of hits per second.
17.3. The number of transactions per second.
17.4. The number of pages per minute.
17.5. Transaction response time.
Question-18. What is the significance of Correlation? Also, highlight automatic correlation.
Correlation is a technique where dynamic values are not hard-coded in your script but are extracted at run-time to avoid failure.
The dynamic value could change for each user action or for different users. In both cases, correlation takes care of these values. And it prevents them from failing during execution.
Automated correlation works on predefined correlation rules.
The script is played back and scanned for auto-correlation upon any failure. Vugen identifies the place where the correlation rules work and correlates the value of approval.
Question-19. What is Manual Correlation?
Manual Correlation involves the following actions.
19.1. Identify the dynamic value.
19.2. Find the first occurrence of dynamic value.
19.3. Identify the unique boundaries to capture the dynamic value.
19.4. Write the correlation function “web_reg_save_param” before the request gets the first occurrence of a dynamic value in response.
19.5. This correlation technique uses function Web_reg_save_param() to identify dynamic values in your script. It is important that you playback your script to verify the correlation is done successfully.
Question-20. How do you identify the performance bottlenecks?
Performance Bottlenecks can be detected by using monitors.
20.1. These monitors might be application server monitors, web server monitors, database server monitors, and network monitors.
20.2. They help in finding out the troubled area in our scenario which causes increased response time.
20.3. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc.
Question-21. How to identify what to correlate and what to parameterize?
Any value in the script that changes on each iteration or with different users while replaying needs correlation. Any user input while recording should be parameterized.
Question-22. What is parameterization & why is parameterization necessary in the script?
Replacing hard-coded values within the script with a parameter is called Parameterization. This helps a single virtual user (i.e. <vuser>) to use different data on each run.
This simulates real-life usage of an application as it prevents the server from caching results.
Question-23. What is the difference between transaction and transaction instance in LoadRunner?
A transaction is used to measure the time between executions of certain statements. While a transaction instance is used for performance analysis.
Question-24. While the script is running we find some values that may need to be correlated. Is it possible to do a manual correlation for those values?
NO. It’s not possible to correlate when the script is running. But you can make changes once the script has stopped.
Question-25. How do you determine the number of load generator machines required to run a test?
The size of the load generator required would totally depend on the two points.
25.1. Protocol used to create the script, and
25.2. The configuration of the load generator machine.
Each protocol has a different memory print and this decides how many virtual users can be generated from the given configuration of the machine.
We hope that the list of LoadRunner interview questions will help you to get the desired job profile.
We tried our best to bring all the relevant questions here. With these questions, you can test your skills and assess if you need any improvement.
Since we are at the end of this post, we would love to know if you do have a better answer for any of the questions. If yes, please share it in the comment section. Your reply would help us immensely. And other readers would also get to see a fresh approach.
If you would have liked this post, please float it across social media and in your friend circle.