Documents

Performance Testing interview Q&A.pdf

Categories
Published
of 68
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Description
LOAD RUNNER Learn Basic Introduction & preliminaries of HP – LoadRunner through FAQ's: Q. 1: What is the process of manual correlation in LoadRunner? It is the method adopted for capturing the dynamic data resulting from the server responses & further reusing it in the script. It can be done in two ways like: 1.Manual correlation 2. Auto Correlation Q. 2: What is the Load testing process in LoadRunner? Step 1: Planning the test: Involves development
Transcript
    LOAD RUNNER Learn Basic Introduction & preliminaries of HP  –  LoadRunner through FAQ's: Q. 1: What is the process of manual correlation in LoadRunner? It is the method adopted for capturing the dynamic data resulting from the server responses & further reusing it in the script. It can be done in two ways like: 1.Manual correlation 2. Auto Correlation <<<<<< =================== >>>>>> Q. 2: 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: Creation of the scenarios: 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. Scenarios are created by 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: The load on the server is emulated by instructing multiple Vusers to perform the 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: 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. Step 6: Analyzing test results: During scenario execution, LoadRunner records the performance of the application under different loads. We use LoadRunner's graphs and reports to analyze the application's performance. <<<<<< =================== >>>>>> Q. 3 : When load and performance Testing are done? Load testing is performed after the completion of interface (GUI) testing.  Single user testing focuses on functionality and user interface of a system component, while 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. <<<<<< =================== >>>>>> Q. 4: What are the components of LoadRunner? The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online. <<<<<< =================== >>>>>> Q. 5: What Component of LoadRunner are used for recording a Script? 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. <<<<<< =================== >>>>>> Q. 6: What is a rendezvous point LoadRunner? Rendezvous points are inserted 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. <<<<<< =================== >>>>>> Q. 7: What Component of LoadRunner are used to play Back the script in multi user mode? 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. <<<<<< =================== >>>>>> Q. 8: What is a scenario in LoadRunner? 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. <<<<<< =================== >>>>>> Q. 9 : What is the recording mode for web Vuser script in LoadRunner? 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. <<<<<< =================== >>>>>> Q. 10: Why do we create parameters in LoadRunner? 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. Learn Basic Introduction & preliminaries of HP  –  LoadRunner through FAQ's: Q. 11: What is a correlation in LoadRunner? 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). Corelations are of two types like : 1) Automatic correlation iinvolves setting of some rules for thecorrelation. It can be application server specific. Here values are replaced by data which are created by these rules. 2) Manual correlation, the value we want to correlate is scanned and create correlation is used to correlate. <<<<<< =================== >>>>>> Q. 12: How can we find out as to where correlation is required in LoadRunner? There are two ways to find out the place of use of corelation 1) 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. 2) We can record two scripts and compare them. <<<<<< =================== >>>>>> Q. 13: Where can we set automatic correlation options in LoadRunner? We can set the automatic correlation from web point of view 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. <<<<<< =================== >>>>>>  Q. 14: What is the function to capture dynamic values in the web Vuser script in LoadRunner? Web_reg_save_param function saves dynamic data information to a parameter. <<<<<< =================== >>>>>> Q. 15: When do you disable log in Virtual User Generator in LoadRunner? 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. <<<<<< =================== >>>>>> Q. 16: When do we use standard and extended logs in LoadRunner? Standard Log Option: It creates a standard log of functions and messages sent during script execution to use for debugging. It is suggested to disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled. Extended Log Option: Is selected to create an extended log, including warnings and other messages. We can specify all additional information that needs to be added to the extended log. <<<<<< =================== >>>>>> Q. 17: How do we debug a script in LoadRunner? 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 our 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. <<<<<< =================== >>>>>> Q. 18:How do we write user defined functions in LoadRunner? 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). Few examples of user defined functions are GetVersion, GetCurrentTime, GetPltform etc. <<<<<< =================== >>>>>> Q. 19: What are the changes possible to be made in run-time settings in LoadRunner? The Run Time Settings are: a) Pacing - Has iteration count. b) Log - Needs to Disable the Logging Standard Log
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks