Whats the LoadRunner? LoadRunner is Mercury Interactive Load Testing tool. Whats the LoadRunner Components?

LoadRunner have the five componentsVuser Generator Controller Load Generator Luncher Analysis Whats the Vuser Generator? It captures the end user processes and generated the automated performance testing script. Whats the Controller? It organize, drive, manage, and monitor the load test. Whats the Load Generator? It generates the load by running the vusers. Whats the Luncher? It provides single point of access for all load runner components. Whats the Analysis? It helps you to view and analyze the performance results. Whats the Scenario? Scenario is a file that contains the events that occurs during each testing sessions. Whats the Vuser? In Scenario, LoadRunner replaces human user with Virtual User or Vuser. Vuser emulates the human action working with your application. Whats the Vuser Script? The action that Vuser performance during the scenario are described in the Vuser script. Whats the Transaction? To measures the performance of the server, we define the Transaction. Whats the Load Testing Process? Load Testing process have five stepsPlan Test Create Vuser script Define Scenario Run Scenario Analyze Results Whats the Rendezvous Point? We can insert Rendezvous Points into Vuser script to emulates the heavy load on the server. Whats the Think Time? Think Time represent the actual time that we waited between the steps. What are the section contain by the VuGen while creating a Vuser script? VuGen contain the three sectionVuser Init Section Action Section Vuser end Section Whats the Vuser Init Section? In Vuser Init section, LoadRunner records log in the server. Whats the Action Section? In Action section, LoadRunner records end user activities. Whats the Vuser end Section? In Vuser end section, LoadRunner records log off into the server. How do you edit the script? We can edit the script by inserting the Transaction Points and Rendezvous Points.

Whats the LoadRunner Start-Transaction and its syntax? It start the Transaction on the script and its syntax is that "lr-start-transaction". Whats the LoadRunner End-Transaction and its syntax? It end the Transaction on the script and its syntax is that "lr-end-transaction" Whats .lrs? Its extension of LoadRunner Scenario files. Which component you are using for recording the vuser script? We are using Vugen component for recording the Vuser script. Which component you are using for playback the script? We are using Controller component for playback the script. Whats the Parameterization? Parameterization is script variables which are used to pass many values to server. It emulates the actions of human user. What are changes we can make in Run Time Settings? We can set the Run Logic, Pacing, Log, Think Time. Whats the Run Logic? In Run Logic we can set the number of repititions which are performing by Vuser. Whats the Pacing? In Pacing we can set the time to wait between each repititions. Whats the Log? Log is level of information which we want to gather during run time. Where we can set the number of repititions? We can set the number of repititions in Run Time Settings. Whats the Ramp-Up and where we can set this? Ramp-Up option used to increases the number of Vuser in server and we can set the this option through scenario schedule. Whats the Host? Host is machine which execute the Vuser script. What are process for developing a Vuser script? There are five steps for developing a Vuser ScriptRecord Vuser script Edit Vuser script Change Run Time Setting Run Vuser script in stand alone machine Incorporate the Vuser script into loadrunner scenario Whats the Remote Command Luncher? RCL enables the controller to start the application on the host machine. Whats the LoadRunner Agent? Agent is interface between controller and host machine. How to load LoadRunner Agent? Controller insturct the RCl to lunch the LoadRunner Agent. How many types of Vuser are available in LoadRunner? There are many types of Vuser like DB Vuser, SAP Vuser, Web Vuser, RTE, GUI Vuser. What type of functions are generated and inserted by LoadRunner? LoadRunner generated two types of functionsLR Function Protocol Function Whats the LR function? LR function is obtained the information about the running Vuser. Whats the Protocol Function? Protocol function obtained the information about the type of Vuser. Whats the Scenario Wizard? We can create new scenario through Scenario Wizard.

Whats the Pause command? It will change the status of running vuser to pause. Whats the running Vuser graph? It displays the number of Vusers that execute the Vuser script each seconds of scenario run. Whats the percentile graph? It displays the percentage of transaction which were performed with in given time. Whats the Rendezvous graph? It displays that when Vusers released from rendezvous point and how many Vusers released from each point. How many types of running mode in LoadRunner? LoadRunner provides two types of recording levelHTML based script URL based script What is the HTML based script? HTML based script generates seprated steps for each user actions. What is the URL based script? It records all requests and resources from server. What is extension of LoadRunner result file? .lrr Which language LoadRunner uses? ANSI C How many types of scenario in loadrunner? LoadRunner provides two types of scenarioManual Scenario Goal-Oriented Scenario What is the Manual Scenario? Manual Scenario manages the load test by specifying the number of vuser to run. What is the Goal-Oriented Scenario? Goal-Oriented scenario allows loadrunner controller to create scenarion based on goal which you specified. Which Correlation function you have used? web_reg_save_param How can we view the script? We can view the script through Tree View and Script View. What is the Tree View? Tree view is icon based view. Whats the Script View? Its text based view. What does Result window contain? Result Window open with two panesTree Pane Summary Pane How many types of checkpoints are available in LoadRunner? LoadRunner provides two types of checkpointsText Checkpoints Image Checkpoints Whats the Correlation? Correlation is used to obtained the data which are unique in every time of scrpit run and which are generated by nested queries. How many types of Correlation? Correlation are two typesManual Correlation Automatic Correlation

Whats the Automatic Correlation? Automatic Corrlation is set some rules for correlation. Whats the syntex for think time? lr_think_time Whats the Elasped Time? Its total time take since request is set and obtained the result. -----------------------------------------------------------------------------------------------------------------------Load Runner is HP tool used to test the performance of a software application. Even though there are many other tools to find testing performance of an application, Loadrunner got its own share of advantage due to its unique features and ease of the tool navigation easy to understand the tool functionality. So, in the interviews when ever you get questions about performance testing, you need answer more about how you have used the loadrunner using its functionality and what kind of different testing you have done such as load testing, benchmark testing, stress testing, endurance testing etc And also please compare how you have compared and used existing benchmark test results with previous and new results. For example, we normally conduct a benchmark test for the application initially and take all the measurements in a excel sheet. Examples of measurements will be like below: Sign-in module with 1000 users at a time 10 sec execution time. Sales category module time with 10 users : 5 sec So, after a while you have implemented one more new module, then you need to do benchmark testing again to see if there is any impact on existing module performances. For this we conduct once again the same benchmark test and take measures and compare with the previous results (above). If any existing module taking more time after this new module implementation, we will investigate why?? 1. What components are available in LoadRunner? The components available in LoadRunner are the following: Controller, Virtual User Generator (VuGen), Agent processor, Analysis, Monitoring, and books online. 2. Which LoadRunner component is used for recording scripts? The Virtual User Generator (VuGen) is used for script recording. It can be used to create Vuser scripts for a broad range of communication protocols and application types. 3. Which LoadRunner component is used for the playback of a script in the multi-user mode? The Controller can be utilized for script playback in the multi-user mode. Script playback is usually performed during scenario testing where multiple Vuser scripts are executed in a group. 4. How can a LoadRunner script be debugged? Breakpoints and the Run Step-by-Step features of VuGen can be used for debugging and this information is written in the output window. There are debug settings in the Options area that allow the user to set the specifics about the trace that is performed during the execution of the scenario. 5. How does one write a user defined function in LoadRunner? When creating a user-defined function, one must first create the external library that contains the function. This library must then be added to the bin directory of VuGen. Next, the user-defined function can be assigned as a parameter. 6. What is the process for load testing? 1. Test Planning Create a clear test plan in order to be certain that the scenarios that will be developed for testing the application will fulfill the objectives for load testing. 2. Vuser Creation Create scripts for Vusers that have tasks that will be completed by each individual Vuser, by all Vusers together, and those that will be examined as transactions. 3. Scenario Creation Scenarios explain the actions that will occur during testing and include lists of scripts, machines, Vusers, etc. that run in that time period. LoadRunner can

automatically build scenarios. The LoadRunner Controller is used for this and it is capable of creating both goal-oriented and manual scenarios. For goal-oriented scenarios, the goal that the test has to achieve is defined. For manual scenarios, the scripts, load generators, volume of Vusers, and amount of Vusers that are to be appointed to each script has to be defined. 4. Scenario Runs Before running the test, the configuration and scheduling of the scenario is set. Running the test will involve instructing several Vusers to execute tasks at the same time, which emulates the load on a server. 5. Scenario monitoring The scenario is monitored using some or all of the many performance monitors offered by LoadRunner. These monitors include the following: system, ERP, web, web application server resource, streaming media, firewall, and database server resources, transaction, online runtime, network delay, and Java performance. 6. Results Analysis LoadRunner records data from the test and provides various reports and graphs that can be used to evaluate the performance of the application. 7. Define rendezvous point. Rendezvous points are places in the test execution that command Vusers to wait for other Vusers so that a task(s) can be performed simultaneously. This is done to simulate heavy user traffic on a server. For example, the peak load for a bank server can be simulated by inserting a rendezvous point that instructs 1000 Vusers to withdraw cash from accounts simultaneously. 8. Why is it useful to establish parameters? Parameters can be thought of as script variables and are used to simulate real users and alter input to the server. It allows the tester to use a single script to emulate a variety of system users by allowing multiple sets of data to be sent to the server with each script run. 9. Which function is used to capture dynamic data in the web Vuser script? Web_reg_save_param is the function that saves dynamic data to a parameter. 10. What are the changes that can be made to run-time settings? There are four run-time settings that can be made: Pacing: This contains iteration count. Log: This is where logging can be set to standard or disabled. Extended Think Time: Capable of setting think time to be ignored or replayed. General: Allows the setting of Vusers for processes or multithreading. 11. How can web server related issues be found? Web resource monitors can be used to find server related issues. These monitors are capable of analyzing web server throughput, volume of hits per second during the execution of the scenario, the number of pages downloaded per second, and the volume of responses per second. 12. How can database related issues be found? Monitors and the Data Resource Graph can be used to find database related issues. LoadRunner allow the tester to specify the resource that is to be measured before the controller is run. Some more Loadrunner Interview Questions. 13. What are the types of options are available for goal-oriented scenarios? There are five goal options available: Number of Vusers (concurrent) Number of transactions/second Number of hits/second Number of pages/minute Transaction response time 14. How many types of graphs are available in LoadRunner and what are they? There are 5 types of graphs: Network delay time graph displays the time the elapses between request and response Two transaction response time graphs one for load and one for percentile

Hits/second graph Shows application traffic volume. Pages download/second graph shows the rate that download processes are performed 15. How can performance bottlenecks be identified? LoadRunner has monitors that can be used to detect performance bottlenecks. These include network, web server, application server, and database server monitors. These monitors can be used to locate trouble spots in scenarios that cause increases response time and they track throughput, network delays, performance response time, hits/sec, etc. 16. When should load and performance testing be performed? Load testing should be performed when the user interface is completed and tested. User interface testing typically focuses on functionality of a system component, whereas load and performance testing focuses on the whole system. For example, a typical scenario will check reliability when 1000 users are logged in at the same time and will examine system response time, operation on various platforms, whether the system crashes, etc. 17. How can one tell when correlation can be performed? There are two ways to do this. One is to use the scan function to search for correlations and select a value from the resulting list. The second is to record a pair of scripts and then compare them to each other. 18. Where are automatic correlation options set? The automatic correlation is set in recording options area on the correlation tab. From here, correlation can be enabled for the full script and rules for correlation can be defined. Automatic correlation can be performed on a database by viewing the output window, scanning for correlation, and selecting the value that will be used. 19. Where is the number of iterations set for testing with Vuser scripts? The number of iterations is set in the VuGen pacing tab in the Run-time settings area. 20. What is ramp up and how can it be set? Ramp up is gradually increasing the load on a server. This is simulated by gradually increasing the number of Vusers. This feature can be found in the Scenario Scheduling Options. When used, the initial value and the time to wait between periods are specified. 21. What is the benefit of running a Vuser script as a thread? The advantage of running a Vuser script as a thread is that it allows more Vusers to be used for one load generator. Running Vuser scripts as processes utilizes a lot of memory because all of the loaded scripts use the same driver. This limits the number of Vuser scripts that can be run on one generator. 22. How do you set LoadRunner to stop script execution when an error occurs? Execution of Vuser scripts can be stopped on error using LoadRunners lr_abort function. The "Continue on error" option must not be checked in the Run-Time Setting menu. It is helpful when it is necessary to abort execution when a certain error condition occurs. This function instructs the Vuser to stop performing what is in the Actions section, and to begin performing the vuser_end functions. When execution is terminated, the Vuser status is changed to "Stopped". 23. How are throughput and response time related? The graph for throughput displays the quantity of data that the server sent to the Vusers in one second. When throughput is compared to the response time of transaction, it decreased as the response time decreased. In addition to this, the highest throughput and response times occur at approximately the same time. 24. Define think time and explain how do you change the threshold for it. Think time is the interval of time that a user must wait between actions. An example of this is the time that a user takes to review data after receiving it from the server before responding to it. The threshold is the maximum level at which this time will be ignored. The default threshold value is five seconds but this can be modified in the VuGen Recording options. 25. Explain the difference between standard and extended log.

The standard log contains a subset of functions and messages, which vary based on the type of Vuser, that are generated during the execution of a script. The extended log creates a more detailed listing of functions and messages. ----------------------------------------------------------------------------------------------------------------------Q1. What is load testing? Ans. Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine weather it can handle peak usage periods. Q2. What is Performance testing? Ans. Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction. Q3. What is LoadRunner? Ans. LoadRunner works by creating virtual users who take the place of real users operating client software, such as sending requests using the HTTP protocol to IIS or Apache web servers. Requests from many virtual user clients are generated by Load Generators in order to create a load on various servers under test these load generator agents are started and stopped by Mercury's Controller program. The Controller controls load test runs based on Scenarios invoking compiled Scripts and associated Run-time Settings. Scripts are crafted using Mercury's "Virtual user script Generator" (named "V U Gen"), It generates C-language script code to be executed by virtual users by capturing network traffic between Internet application clients and servers. With Java clients, VuGen captures calls by hooking within the client JVM. During runs, the status of each machine is monitored by the Controller. At the end of each run, the Controller combines its monitoring logs with logs obtained from load generators, and makes them available to the "Analysis" program, which can then create run result reports and graphs for Microsoft Word, Crystal Reports, or an HTML webpage browser. Each HTML report page generated by Analysis includes a link to results in a text file which Microsoft Excel can open to perform additional analysis. Errors during each run are stored in a database file which can be read by Microsoft Access. Q4. What is Virtual Users? Ans. Unlike a WinRunner workstation which emulates a single user's use of a client, LoadRunner can emulate thousands of Virtual Users.Load generators are controlled by VuGen scripts which issue non-GUI API calls using the same protocols as the client under test. But WinRunner GUI Vusers emulate keystrokes, mouse clicks, and other User Interface actions on the client being tested. Only one GUI user can run from a machine unless LoadRunner Terminal Services Manager manages remote machines with Terminal Server Agent enabled and logged into a Terminal Services Client session. During run-time, threaded users share a common memory pool. So threading supports more Vusers per load generator. The Status of Vusers on all load generators start from "Running", then go to "Ready" after going through the init section of the script. Vusers are "Finished" in passed or failed end status. Vusers are automatically "Stopped" when the Load Generator is overloaded. To use Web Services Monitors for SOAP and XML, a separate license is needed, and vUsers require the Web Services add-in installed with Feature Pack (FP1). No additional license is needed for standard web (HTTP) server monitors Apache, IIS, and Netscape. Q5. Explain the Load testing process? Ans. Step 1: Planning the test. Here, we develop a clearly defined test plan to ensure the test scenarios we develop will accomplish load-testing objectives. Step 2: Creating Vusers. Here, we create Vuser scripts that contain tasks performed by each Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions.

Step 3: Creating the scenario. A scenario describes the events that occur during a testing session. It includes a list of machines, scripts, and Vusers that run during the scenario. We create scenarios using LoadRunner Controller. We can create manual scenarios as well as goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load generator machines, and percentage of Vusers to be assigned to each script. For web tests, we may create a goal-oriented scenario where we define the goal that our test has to achieve. LoadRunner automatically builds a scenario for us. Step 4: Running the scenario. We emulate load on the server by instructing multiple Vusers to perform tasks simultaneously. Before the testing, we set the scenario configuration and scheduling. We can run the entire scenario, Vuser groups, or individual Vusers. Step 5: Monitoring the scenario. We monitor scenario execution 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. Step 6: Analyzing test results. During scenario execution, LoadRunner records the performance of the application under different loads. We use LoadRunners graphs and reports to analyze the applications performance. Q6. When do you do load and performance Testing? Ans. We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing. Q7. What are the components of LoadRunner? Ans. The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online. Q8. What Component of LoadRunner would you use to record a Script? Ans. The Virtual User Generator (VuGen) component is used to record a script. It enables you to develop Vuser scripts for a variety of application types and communication protocols. Q9. When do you do load and performance Testing? Ans. We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing. Q10. What are the components of LoadRunner? Ans. The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online. What Component of LoadRunner would you use to record a Script? - The Virtual User Generator (VuGen) component is used to record a script. It enables you to develop Vuser scripts for a variety of application types and communication protocols. Q11. What Component of LoadRunner would you use to play Back the script in multi user mode? Ans. The Controller component is used to playback the script in multi-user mode. This is done during a scenario run where a vuser script is executed by a number of vusers in a group. Q12. What is a rendezvous point?

Ans. You insert rendezvous points into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to arrive at a certain point, in order that they may simultaneously perform a task. For example, to emulate peak load on the bank server, you can insert a rendezvous point instructing 100 Vusers to deposit cash into their accounts at the same time. Q13. What is a scenario? Ans. A scenario defines the events that 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 machines on which the virtual users run their emulations. Q14. Explain the recording mode for web Vuser script? Ans. We use VuGen to develop a Vuser script by recording a user performing typical business processes on a client application. VuGen creates the script by recording the activity between the client and the server. For example, in web based applications, VuGen monitors the client end of the database and traces all the requests sent to, and received from, the database server. We use VuGen to: Monitor the communication between the application and the server; Generate the required function calls; and Insert the generated function calls into a Vuser script. Q15. Why do you create parameters? Ans. Parameters are like script variables. They are used to vary input to the server and to emulate real users. Different sets of data are sent to the server each time the script is run. Better simulate the usage model for more accurate testing from the Controller; one script can emulate many different users on the system. Q16. What is correlation? Ans. Correlation is used to obtain data which are unique for each run of the script and which are generated by nested queries. Correlation provides the value to avoid errors arising out of duplicate values and also optimizing the code (to avoid nested queries). Automatic correlation is where we set some rules for correlation. It can be application server specific. Here values are replaced by data which are created by these rules. In manual correlation, the value we want to correlate is scanned and create correlation is used to correlate. Q17. How do you find out where correlation is required? Ans. Two ways: First we can scan for correlations, and see the list of values which can be correlated. From this we can pick a value to be correlated. Secondly, we can record two scripts and compare them. We can look up the difference file to see for the values which needed to be correlated. Q18. Where do you set automatic correlation options? Ans. Automatic correlation from web point of view can be set in recording options and correlation tab. Here we can enable correlation for the entire script and choose either issue online messages or offline actions, where we can define rules for that correlation. Automatic correlation for database can be done using show output window and scan for correlation and picking the correlate query tab and choose which query value we want to correlate. If we know the specific value to be correlated, we just do create correlation for the value and specify how the value to be created. Q19. What is a function to capture dynamic values in the web Vuser script? Ans. Web_reg_save_param function saves dynamic data information to a parameter. Q20. Which is VuGen Recording and Scripting language? Ans. LoadRunner script code obtained from recording in the ANSI C language syntax, represented by icons in icon view until you click Script View. Q21. What is Scenarios? Ans. Scenarios encapsulate the Vuser Groups and scripts to be executed on load generators at run-time. Manual scenarios can distribute the total number of Vusers among scripts based on the analyst-specified percentage (evenly among load generators). Goal Oriented scenarios are

automatically created based on a specified transaction response time or number of hits/transactions-per-second (TPS). Test analysts specify the % of Target among scripts. Q22. When do you disable log in Virtual User Generator, When do you choose standard and extended logs? Ans. Once we debug our script and verify that it is functional, we can enable logging for errors only. When we add a script to a scenario, logging is automatically disabled. Standard Log Option: When you select Standard log, it creates a standard log of functions and messages sent during script execution to use for debugging. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled Extended Log Option: Select extended log to create an extended log, including warnings and other messages. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled. We can specify which additional information should be added to the extended log using the Extended log options. Q23. How do you debug a LoadRunner script? Ans. VuGen contains two options to help debug Vuser scripts-the Run Step by Step command and breakpoints. The Debug settings in the Options dialog box allow us to determine the extent of the trace to be performed during scenario execution. The debug information is written to the Output window. We can manually set the message class within your script using the lr_set_debug_message function. This is useful if we want to receive debug information about a small section of the script only. Q24. How do you write user defined functions in LR? Ans. Before we create the User Defined functions we need to create the external library (DLL) with the function. We add this library to VuGen bin directory. Once the library is added then we assign user defined function as a parameter. The function should have the following format: __declspec (dllexport) char* (char*, char*) Q25. What are the changes you can make in run-time settings? Ans. The Run Time Settings that we make are: Pacing - It has iteration count. Log - Under this we have Disable Logging Standard Log and Extended Think Time - In think time we have two options like Ignore think time and Replay think time. General - Under general tab we can set the vusers as process or as multithreading and whether each step as a transaction. Q26. Where do you set Iteration for Vuser testing? Ans. We set Iterations in the Run Time Settings of the VuGen. The navigation for this is Run time settings, Pacing tab, set number of iterations. Q27. How do you perform functional testing under load? Ans. Functionality under load can be tested by running several Vusers concurrently. By increasing the amount of Vusers, we can determine how much load the server can sustain. Q28. How to use network drive mappings? Ans. If several load generators need to access the same physical files, rather than having to remember to copy the files each time they change, each load generator can reference a common folder using a mapped drive. But since drive mappings are associated with a specific user: Logon the load generator as the user the load generator will use Open Windows Explorer and under Tools select Map a Network Drive and create a drive. It saves time and hassle to have consistent drive letters across load generators, so some organizations reserver certain drive letters for specific locations. Open the LoadRunner service within Services (accessed from Control Panel, Administrative Tasks), Click the "Login" tab. Specify the username and password the load generator service will use. (A dot appears in front of the username if the userid is for the local domain).

Stop and start the service again. Q29. What is Ramp up? How do you set this? Ans. This option is used to gradually increase the amount of Vusers/load on the server. An initial value is set and a value to wait between intervals can be specified. To set Ramp Up, go to Scenario Scheduling Options. Q30. What is the advantage of running the Vuser as thread? Ans. VuGen provides the facility to use multithreading. This enables more Vusers to be run pergenerator. If the Vuser is run as a process, the same driver program is loaded into memory for each Vuser, thus taking up a large amount of memory. This limits the number of Vusers that can be run on a single generator. If the Vuser is run as a thread, only one instance of the driver program is loaded into memory for the given number of Vusers (say 100). Each thread shares the memory of the parent driver program, thus enabling more Vusers to be run per generator. Q31. If you want to stop the execution of your script on error, how do you do that? Ans. The lr_abort function aborts the execution of a Vuser script. It instructs the Vuser to stop executing the Actions section, execute the vuser_end section and end the execution. This function is useful when you need to manually abort a script execution as a result of a specific error condition. When you end a script using this function, the Vuser is assigned the status "Stopped". For this to take effect, we have to first uncheck the Continue on error option in Run-Time Settings. Q32. What is the relation between Response Time and Throughput? Ans. The Throughput graph shows the amount of data in bytes that the Vusers received from the server in a second. When we compare this with the transaction response time, we will notice that as throughput decreased, the response time also decreased. Similarly, the peak throughput and highest response time would occur approximately at the same time. Q33. Explain the Configuration of your systems? Ans. The configuration of our systems refers to that of the client machines on which we run the Vusers. The configuration of any client machine includes its hardware settings, memory, operating system, software applications, development tools, etc. This system component configuration should match with the overall system configuration that would include the network infrastructure, the web server, the database server, and any other components that go with this larger system so as to achieve the load testing objectives. Q34. How do you identify the performance bottlenecks? Ans. Performance Bottlenecks can be detected by using monitors. These monitors might be application server monitors, web server monitors, database server monitors and network monitors. They help in finding out the troubled area in our scenario which causes increased response time. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc. Q35. If web server, database and Network are all fine where could be the problem? Ans. The problem could be in the system itself or in the application server or in the code written for the application. Q36. How did you find web server related issues? Ans. Using Web resource monitors we can find the performance of web servers. Using these monitors we can analyze throughput on the web server, number of hits per second that occurred during scenario, the number of http responses per second, the number of downloaded pages per second. Q37. How did you find database related issues? Ans. By running Database monitor and help of Data Resource Graph we can find database related issues. E.g. you can specify the resource you want to measure on before running the controller and than you can see database related issues. Q38. What is the difference between Overlay graph and Correlate graph? Ans. Overlay Graph: It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph shows the current graphs value & Right Y-axis show the value

of Y-axis of the graph that was merged. Correlate Graph: Plot the Y-axis of two graphs against each other. The active graphs Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graphs Y-axis. Q39. How did you plan the Load? Ans. Load test is planned to decide the number of users, what kind of machines we are going to use and from where they are run. It is based on 2 important documents, Task Distribution Diagram and Transaction profile. Task Distribution Diagram gives us the information on number of users for a particular transaction and the time of the load. The peak usage and off-usage are decided from this Diagram. Transaction profile gives us the information about the transactions name and their priority levels with regard to the scenario we are deciding. Q40. What does vuser_init action contain? Ans. Vuser_init action contains procedures to login to a server. Q41. What does vuser_end action contain? Ans. Vuser_end section contains log off procedures. Q42. What is think time? Ans. Think time is the time that a real user waits between actions. Example: When a user receives data from a server, the user may wait several seconds to review the data before responding. This delay is known as the think time. Changing the Threshold: Threshold level is the level below which the recorded think time will be ignored. The default value is five (5) seconds. We can change the think time threshold in the Recording options of the Vugen. Q43. What is the difference between standard log and extended log? Ans. The standard log sends a subset of functions and messages sent during script execution to a log. The subset depends on the Vuser type Extended log sends a detailed script execution messages to the output log. This is mainly used during debugging when we want information about: - Parameter substitution - Data returned by the server - Advanced trace Q44. What is lr_debug_message? Ans. The lr_debug_message function sends a debug message to the output log when the specified message class is set. Q45. What is lr_output_message? Ans. The lr_output_message function sends notifications to the Controller Output window and the Vuser log file. Q46. What is lr_error_message? Ans. The lr_error_message function sends an error message to the LoadRunner Output window. Q47. What is lrd_stmt? Ans. The lrd_stmt function associates a character string (usually a SQL statement) with a cursor. This function sets a SQL statement to be processed. Q48. What is lrd_fetch? Ans. The lrd_fetch function fetches the next row from the result set. Q49. What is Throughput? Ans. If the throughput scales upward as time progresses and the number of Vusers increase, this indicates that the bandwidth is sufficient. If the graph were to remain relatively flat as the number of Vusers increased, it would be reasonable to conclude that the bandwidth is constraining the volume of data delivered. Q50. What are the various types of Goals in Goal-Oriented Scenario ? Ans. Load Runner provides you with five different types of goals in a goal oriented scenario: - 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 that you want your scenario Analysis Scenario (Bottlenecks): In Running Vuser graph correlated with the response time graph you can see that as the number of Vusers increases, the average response time of the check itinerary transaction very gradually increases. In other words, the average response time steadily increases as the load increases. At 56 Vusers, there is a sudden, sharp increase in the average response time. We say that the test broke the server. That is the mean time before failure (MTBF). The response time clearly began to degrade when there were more than 56 Vusers running simultaneously. ------------------------------------http://www.qualitytrainings.com/Loadrunner_interview_questions_and_answers