Most Frequently asked LoadRunner Interview Questions.
In our previous tutorial, we explored all about Test Result Analysis in LoadRunner.
This article is going to focus on the most important commonly asked LoadRunner interview questions and answers that will help you be successful in any performance tester’s interview using LoadRunner.
LoadRunner is one of the best-licensed Performance Testing tools in the market. It is best suited for most of the upcoming technologies because of the wide range of supported protocols.
A few basic pointers before we begin:
#1) LoadRunner interview questions can be categorized into 3 main types – Scripting, Execution, and Analysis. It is important for beginners to focus more on the scripting part.
#2) Http/HTML is mostly used Protocol, for a start try to perfect this protocol.
#3) Be sure to know the exact version of LoadRunner that you worked on. In case of work experience with a previous version, try to keep yourself updated with the features that are part of the newer/current versions.
#4) Performance Testing interviews are more practical than they used to be. Scenario oriented questions are common rather than straightforward ones. Some companies, even make scripting tests a part of the interview process. So, be prepared for the same.
#5) Even in scripting, it is preferred that you be able to customize code, instead of just record and replay.
#6) Expect questions on – think time, transactions, comments, recording options, runtime settings, etc. – these are to test your knowledge of scripting best practices.
The following are some of the Performance Testing interview questions that will need some experience to answer. Try to keep these questions in mind while working on your performance test projects, so the interview preparation activity becomes a continuous process.
- What are the different scripting issues you faced so far?
- What are the performance bottlenecks that you found in the projects you were working on? What are the recommendations made to overcome those issues?
- Have you applied Little's law to your project? If so, how?
- What is your approach for analysis?
- What do you monitor while execution?
- How to extract server data for test execution and how to analyze that?
- How to identify performance bottlenecks?
Key question areas are:
- Challenges that you face during scripting
- Correlation function
- Error handling
- Different recording modes for Web HTTP/HTML protocol.
- Scenario creation
- Challenges during execution
Below we have provided a few common LoadRunner interview questions and answers to them. However, please note that the best results can be achieved by providing answers based on your exposure, expertise, and interpretation of the concepts. Learning just the answers to questions is not always optimum. Practice, Learn and Expert – this should be your approach for Performance Testing interview preparation.
LoadRunner Interview Questions And Best Answers
Q #1) What is the difference between Performance Testing and Performance engineering?
Answer: In Performance Testing, testing cycle includes requirement gathering, scripting, execution, result sharing, and report generation. Performance Engineering is a step ahead of Performance Testing where after execution; results are analyzed with the aim to find the performance bottlenecks and the solution is provided to resolve the identified issues.
Q #2) Explain Performance Testing Life Cycle.
- Step 1: System Analysis (Identification of critical transaction)
Virtual User Generator
- Step 2: Creating Virtual User Scripts (Recording)
- Step 3: Defining Users Behavior (Runtime setting)
- Step 4: Creating Load Test Scenarios
- Step 5: Running the Load Test Scenarios and Monitoring the Performance
- Step 6: Analyzing the Results
Refer Performance Testing Tutorial #2 for more details.
Q #3) What is Performance Testing?
Answer: Performance Testing is done to evaluate the application's performance under load and stress conditions. It is generally measured in terms of the response time of the user’s action on an application.
Q #4) What is Load Testing?
Answer: Load Testing is to determine if an application can work well with the heavy usage resulting from a large number of users using it simultaneously. The load is increased to simulates the peak load that the servers are going to take during maximum usage periods.
Q #5) What are the different components of LoadRunner?
The major components of LoadRunner are:
- VUGen: Records Vuser scripts that emulate the actions of real users.
- Controller: Administrative center for creating, maintaining and executing load test scenarios. Assigns scenarios to Vusers and load generators, starts and stops loading tests.
- Load Generator: An agent through which we can generate load
- Analysis: Provides graphs and reports that summarize the system performance
Q #6) What is the Rendezvous point?
Answer: Rendezvous point helps in emulating heavy user load (request) on the server. This instructs Vusers to act simultaneously. When the Vuser reaches the Rendezvous point, it waits for all Vusers with Rendezvous point. Once designated numbers of Vusers reaches it, the Vusers are released. Function lr_rendezvous is used to create the Rendezvous point. This can be inserted by:
- Rendezvous button on the floating Recording toolbar while recording.
- After recording Rendezvous point is inserted through Insert> Rendezvous.
Q #7) What are the different sections of the script? In what sequence do these sections run?
Answer: LoadRunner script has three sections Vuser_init, Action, and Vuser_end.
- Vuser_init has requests/actions to login to the application/server.
- Action has actual code to test the functionality of the application. This can be played many times in iterations.
- Vuser_end has requests/actions to login out of the application/server.
The sequence in which these sections get executed is Vuser_init is at the very beginning and Vuser_end at the very end. The action is executed in between the two.
Q #8) How do you identify which protocol to use for any application?
Answer: Previously Performance tester had to depend much on the development team to know about the protocol that the application is using to interact with the server. Sometimes, it also used to be speculative.
However, LoadRunner provides great help in the form of Protocol Advisor from version 9.5 onwards. Protocol advisor detects the protocols that the application uses and suggests to us the possible protocols in which script can be created to simulate the real user.
Q #9) What is a Correlation? Explain the difference between Automatic Correlation and Manual Correlation?
Answer: Correlation is used to handle the dynamic values in a script. The dynamic value could change for each user action (value changes when action is replayed by the same user) or for different users (value changes when action is replayed with a different user). In both cases, correlation takes care of these values and prevents them from failing during execution.
Manual Correlation involves identifying the dynamic value, finding the first occurrence of dynamic value, identifying the unique boundaries of capturing the dynamic value, writing correlation function web_reg_save_param before the request having the first occurrence of a dynamic value in its response.
Automated correlation works on predefined correlation rules. The script is played back and scanned for autocorrelation on failing. Vugen identifies the place wherever the correlation rules work and correlate the value on approval.
Refer to this tutorial for more details.
Q #10) How to identify what to correlate and what to parameterize?
Answer: Any value in the script that changes on each iteration or with the different users while replaying needs correlation. Any user input while recording should be parametrized.
Q #11) What is Parameterization & why is Parameterization necessary in the script?
Answer: Replacing hard-coded values within the script with a parameter is called Parameterization. This helps a single virtual user (Vuser) to use different data on each run. This simulates real-life usage of an application as it avoids server from caching results.
Refer to this tutorial for more details.
Q #12) How you identify Performance test use cases of any application?
Answer: Test cases/Uses cases for Performance tests are almost the same as any Manual/Functional testing test cases where each and every step performed by the user is written. The only difference is that all Manual test cases can’t be Performance Testing use cases as there are few criteria for the selection as:
- The user activity should be related to the critical and most important functionality of the application.
- The user activity should be having a good amount of database activity such as search, delete or insert.
- The user activity should be having good user volume. The functionality of having less user activity is generally omitted from the Performance testing point of view. For Example, admin account activity.
Any of the Manual test cases that fulfill the above criteria can be used as a Performance Testing use case/test case. If manual test cases are not written step by step, the Performance team should create dedicated documents for them.
Q #13) While scripting you created correlation rules for Automatic Correlation. If you want to share the correlation rules with your team members working on the same application so that he/she can use the same on his workstation, how will you do that?
Answer: Correlation rules can be exported through the .cor file and the same file can be imported through VuGen.
Q #14) What are different types of Vuser logs that can be used while scripting and execution? What is the difference between these logs? When you disable logging?
Answer: There are two types of Vuser logs available –Standard log and Extended log. Logs are key for debugging the script. Once a script is up and running, logging is enabled for errors only.
Standard log creates a log of functions and messages sent to the server during script execution whereas the Extended log contains additional warnings and other messages. Logging is used during debugging and disabled while execution. Logging can be enabled for errors in that case.
Q #15) What is the Modular approach of scripting?
Answer: In Modular approach, a function is created for each request (For Example, login, logout, save, delete, etc.) and these functions are called wherever required. This approach gives more freedom to reuse the request and saves time. With this approach, it is recommended to work with web custom requests.
Q #16) What are the different types of goals in Goal-Oriented Scenario?
Answer: LoadRunner has five different types of goals in Goal-Oriented Scenario. These are:
- The number of concurrent Vusers
- The number of hits per second
- The number of transactions per second
- The number of pages per minute
- The transaction response time
Q #17) How is each step validated in the script?
Answer: Each step in the script is validated with the content on the returned page. A content check verifies whether specific content is present on the web page or not. There are two types of a content check which can be used in LoadRunner:
- Text Check: This checks for a text/string on the web page.
- Image Check: This checks for an image on a web page.
Q #18) How is the VuGen script modified after recording?
Answer: Once the script is recorded, it can be modified with the following process:
- Variable declarations
- Rendezvous Point
Q #19) What are Ramp-up and Ramp Down?
- Ramp-up: Rate at which virtual users add to the load test.
- Ramp Down: Rate at which virtual users exit from the load test.
Q #20) What is the advantage of running the Vuser as the thread?
Answer: Running Vusers as thread helps generate more virtual users from any machine due to the small memory print of the Vuser running a thread.
Q #21) What is wasted time in the VuGen Replay log?
Answer: Waste time is never performed by any browser user and just the time spent on the activities which support the test analysis. These activities are related to logging, keeping record and custom analysis.
Q #22) How do you enable text and image checks in VuGen?
Answer: This can be done by using functions web_find (for text check) and web_image_check (for image check) and enabling image and text check from runtime setting.
Run Time Setting–>Preference–>Enable the Image and text checkbox.
Q #23) What is the difference between web_reg_find and web_find?
Answer: web_reg_find function is processed before the request sent and is placed before the request in the VuGen script whereas a web_find function is processed after the response of the request comes and is placed after the request in VuGen script.
Q #24) What are the challenges that you will face to script the step “Select All” and then “Delete” for any mail account?
Answer: In this case, the post for “Select All” and “Delete” will change every time depending on the number of mails available. For this the recorded request for the two should be replaced with the custom request and string building is required to build the post. (Note– This question needs practical knowledge. So please this practically and formulate your answer).
Q #25) What is a difference between pacing and think time?
Answer: Pacing is the wait time between the action iterations whereas thinking the time is a wait time between the transactions.
Q #26) What is the number of graphs you can monitor using Controller at a time? What is the max of them?
Answer: One, two, four and eight graphs can be seen at a time. The maximum number of graphs that can be monitored at a time is 8.
Q #27) You have an application that shows the exam results of the student. Corresponding to the name of each student its mentioned whether he passed or failed the exam with the label of “Pass” and “Fail”. How will you identify the number of passed and failed students in the VuGen script?
Answer: For this text check is used for the web page for the text “Pass and “Fail”. Through the function web_reg_find, we can capture the number of texts found on the web page with the help of “SaveCount”. SaveCount stored the number of matches found. For example-
web_reg_find("Text=Pass", "SaveCount=Pass_Student", LAST); web_reg_find("Text=Fail", "SaveCount=Fail_Student", LAST);
Q #28) During the load test, what is the optimum setting for Logs?
Answer: For the load test log level is set to minimal. This can be achieved by setting the log level to the standard log and selecting the radio button “Send a message only when an error occurs”.
Q #29) How will you handle the situation in scripting were for your mailbox you have to select any one mail randomly to read?
Answer: For this, we will record the script for reading the first mail. Try to find what is being posted in the request to read the first mail such as mail ids or row no.
From the post where a list of emails is reflecting, we will try to capture all the email ids row no with correlation function and keeping Ordinal as All i.e. ORD=All. Replace the requested email id in the read post with any of the randomly selected email id from the list of captured email ids.
Refer to this Scripting Tutorial.
Q #30) What is the Think Time? What is the Threshold level for think time and how can be this changed?
Answer: Think time is the wait time inserted intentionally between the actions in the script to emulate real user`s wait time while performing an activity on the application. The Threshold level for Think time in the level below which recorded think time will be ignored. This can be changed from Recorded options->Script->Generate think time greater than the threshold.
Q #31) How is the Automated Correlation configured?
Answer: Any setting related to Automated Correlation can be done by General Options->Correlation. Correlation rules are set from Recording options->Correlations.
Q #32) How do you decide the number of load generator machines required to run a test?
Answer: The number of load generators required totally depends on the protocol used to create the script and 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 give configuration of the machine (load generator).
Q #33) What are the capabilities exactly you look for while selecting the performance testing tool?
Answer: Performance testing tool should capable of:-
- Testing an application built using multiple technologies and hardware platforms.
- Determine the suitability of a server for testing the application
- Testing an application with a load of tens, thousand and even thousands of virtual users.
Q #34) How are concurrent users differing from simultaneous users?
Answer: All simultaneous users are concurrent users but vice versa is not true.
All the Vusers in the running scenario are Concurrent users as they are using the same application at the same time but maybe or may not be doing the same tasks. Simultaneous users perform the same task at the same time. Concurrent users are made Simultaneous users through rendezvous points.
Rendezvous points instruct the system to wait until a certain number of Vusers arrive so that they all can do a particular task simultaneously.
Q #35) How do you identify which values need to be correlated in the script? Give an example.
Answer: This can be done in ways:
- Record the two scripts with similar steps and compare them using WDiff utility. (See tutorial Correlation).
- Replay the recorded script and scan for correlation. This gives a list of values that can be correlated.
Session-Id is a good example of this. When two scripts are recorded and compared using WDiff utility. Session ids in the two scripts should be different and WDiff highlights these values.
Q #36) How does caching affect Performance Testing results?
Answer: When data is cached in the server's memory, the server needs not to fetch the result and no server activity triggered. The test result does not reflect the same performance of real users using the application with different data.
Q #37) How will you stop the execution of a script on error?
Answer: This can be achieved through lr_abort function. The function instructs the Vuser to stop executing the Action section and end the execution by executing the vuser_end section. This function is helpful in handling a specific error.
This can also be used to handle a situation rather than error where execution is not possible. The function assigned “Stopped” status to the Vuser which stopped due to lr_abort function. In the Run-Time setting, “Continue on error” should be unchecked.
Over to you
We hope this huge compilation of LoadRunner interview questions with answers will prove useful to you all.
At STH, we always profess the importance of fundamentals. The same is true to succeed in the performance test professional as well. However, we wish that this performance testing interview questionnaire will be an instrumental reference point for all of you aspiring to find or advance in a performance testing career using LoadRunner.
Wish you all the very best!
I hope you enjoyed the whole range of tutorials in this LoadRunner Series.