Software Testing Interview Questions - Load Runner Interview question

1. What is load testing?
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.

2. What is Performance testing?
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.

3. Did u use LoadRunner? What version?
Yes. Version 7.2.

4. Explain the Load testing process?
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 LoadRunner’s graphs and reports to analyze the application’s performance.

5. When do you do load and performance Testing?
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.

6. 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.

7. 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.

8. What Component of LoadRunner would you use to play Back the script in multi user mode?
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.

9. What is a rendezvous point?
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.

10. What is a scenario?
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.

11. Explain the recording mode for web Vuser script?
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.

12. Why do you create parameters?
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.

13. What is correlation?Explain the difference between automatic correlation and manual correlation?
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.

14. How do you find out where correlation is required? Give few examples from your projects?
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. In my project, there was a unique id developed for each customer, it was nothing but Insurance Number, it was generated automatically and it was sequential and this value was unique. I had to correlate this value, in order to avoid errors while running my script. I did using scan for correlation.

15. Where do you set automatic correlation options?
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.

16. What is a function to capture dynamic values in the web Vuser script?
Web_reg_save_param function saves dynamic data information to a parameter.

17. When do you disable log in Virtual User Generator, When do you choose standard and extended logs?
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.

18. How do you debug a LoadRunner script?
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.

19. How do you write user defined functions in LR? Give me few functions you wrote in your previous project?
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*)Examples of user defined functions are as follows:GetVersion, GetCurrentTime, GetPltform are some of the user defined functions used in my earlier project.

20. What are the changes you can make in run-time settings?
The Run Time Settings that we make are: a) Pacing - It has iteration count. b) Log - Under this we have Disable Logging Standard Log and c) Extended Think Time - In think time we have two options like Ignore think time and Replay think time. d) General - Under general tab we can set the vusers as process or as multithreading and whether each step as a transaction.

21. Where do you set Iteration for Vuser testing?
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.

22. How do you perform functional testing under load?
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.

23. What is Ramp up? How do you set this?
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’

24. What is the advantage of running the Vuser as thread?
VuGen provides the facility to use multithreading. This enables more Vusers to be run per generator. 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.

25. If you want to stop the execution of your script on error, how do you do that? 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.

26. What is the relation between Response Time and Throughput?
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.

27. Explain the Configuration of your systems?
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.

28. How do you identify the performance bottlenecks?
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.

29. If web server, database and Network are all fine where could be the problem?
The problem could be in the system itself or in the application server or in the code written for the application.

30. How did you find web server related issues?
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.

31. How did you find database related issues?
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

32. Explain all the web recording options?

33. What is the difference between Overlay graph and Correlate graph?
Overlay Graph: It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph show’s the current graph’s 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 graph’s Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graph’s Y-axis.

34. How did you plan the Load? What are the Criteria?
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.

35. What does vuser_init action contain?
Vuser_init action contains procedures to login to a server.

36. What does vuser_end action contain?
Vuser_end section contains log off procedures.

37. What is think time? How do you change the threshold?
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.

38. What is the difference between standard log and extended log?
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.

39. Explain the following functions: - lr_debug_message
The lr_debug_message function sends a debug message to the output log when the specified message class is set.
lr_output_message
The lr_output_message function sends notifications to the Controller Output window and the Vuser log file.
lr_error_message
The lr_error_message function sends an error message to the LoadRunner Output window. lrd_stmt
The lrd_stmt function associates a character string (usually a SQL statement) with a cursor. This function sets a SQL statement to be processed.
lrd_fetch
The lrd_fetch function fetches the next row from the result set.

40. Throughput
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.

41. Types of Goals in Goal-Oriented Scenario
Load Runner provides you with five different types of goals in a goal oriented scenario:
o The number of concurrent Vusers
o The number of hits per second
o The number of transactions per second
o The number of pages per minute
o The transaction response time that you want your scenario

42. 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.

43. What is correlation? Explain the difference between automatic correlation and manual correlation?
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.

44. Where do you set automatic correlation options?
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.

45. What is a function to capture dynamic values in the web vuser script?
Web_reg_save_param function saves dynamic data information to a parameter.

Software Testing Interview Questions - Win Runner

) Advantages of Automation Tools in Testing?
a) Minimum requirement of human resource.
b) Accurary.
c) Reliable
d) Less time consuming-Faster than manual testing.
e) Reusable
f) Programmable

2) What is the latest version of WinRunner?
Latest version of WinRunner is 8.0

3) What is the language used in WinRunner?
TSL-Test Scipt Language (Similar to C)

4) Explain the Testing Process in WinRunner?
a) Create a Rapid Test Script Wizard.The Wizard automatically generates a series of tests,Which you can immediately run on your Application.
b) Additional tests can either be created or recorded
c) Debug the test
d) Run the test on new version to verufy the application behavior.

5)What are the components of WinRunner?
a)Test Window : This is a window where the TSL script is generated/programmed.
b)GUI Spy tool in WinRunner lets you spy on the GUI objets by recording the Properties.

6) How does WinRunner identify GUI objects?
The WR examines the GUI objects, and saves the object descriptions in a GUI Map File Later on when you run tests, Win Runner uses this file to identify and locate objects.Win Runner learns desctiption of a GUI object, it looks at the object's physical.Eeach GUI objects has many properties such as "class", "label","width", "height","handle",and "enable" to name a few However, Win Runner only learns the properties that uniquely distinguish an object from all other objects in the application
For example, when Win Runner looks at an Ok button, it might see that the butto9n is located in an Open window, belongs to the pushbutton object class, and has the test label "OK'.

7) What is GUI Spy?
GUI Spy tool in WinRunner lets you spy on the GUI object by recording the propreties.
path: Tools/GUI Spy and start recording.

8) What are all captured in GUI Spy?
a) class to which the object relates.
b)label.
c)Description of the object.

9) What is Rapid Test Script Wizard?
it performs two tasks.
a)It systematically opens the windows in your application and learns a description of Every GUI object.The wizard stores this information in a GUI map file.
b) It automatically generates tests base on the information it learned as it navigated through the application.

10) What is a User Interface test?
The User Interface test compiles an AUT in accordance with microsoft standards.
A user interface test checks the following:
. GUI objects do not overlap
. GUI objects are aligned in windows
. Text labels on GUI objects begin with capital letters
. Text labels on GUI objects are clearly visible
. OK and Cancel buttons appear in every window
. A system menu is available in every window.

11) What are the different modes in learning an application under Rapid test script wizard?
a) Express
b) Comprehensive.

12) What are the different reocd modes?
a) Analog
b) Context Sensitive

13) What is Context Sensitive Mode?
Context Sensitive mode records the operations you perform in terms of the GUI Objects in your application. Win Runner identifies each objects you click (such as a window, menu, list, or button), and the tupe of operation you perform (such as Press,enable, move, or select)

14) What is Analog mode?
In Analog mode, WinRunner records the exact coordinates traveled buy the mouse, as well as mouse clicks and keyboard input.

15) When Context Sensitive mode is to be chosen?
a) The application contains GUI objects
b) Does not require exact mouse movements.

16) When Analog mode is to be chosen?
a) The application contains bitmap areas.
b) Does require exact mouse movements.

17) What are the different run modes?
i) verify: Use verify Mode When rnning a test to check the behaviour of your application,and when your want to save the test results.
ii) Debug: Use Debug Mode when you want to check that the test script runs smoothly without errors in syntax.
iii) Update: Use Update mode when your want to create new expected results for a GUI checkpoint or bitmap checkpoint.

18) What is Synchronization?
When you run tests. your application may not alwayus respond to input with the Same speed .For example, it might take a few seconds:
. to retrive information from a database
. for a window to pop up
. for a progress bar to reach 100%
. for a status message to appear

Win Runner waits a set amount of time for an application to respond to input. The default amount of time that win Runner waits is up to 10 seconds. If the application responds slowly during a test run, WinRunner's default wait time may not be enough, and WinRunner may try to continue the test before the application is ready. The test run, will then unexpectedly fail. If your discover a synchronization problem between the test and uyour application, you can either:

. Increase the default time that the WinRunner waits. to do so, your change thevalue of the timeout test option tin the Options dialog box (Settings Options): This method affects all your tests and slows down many other Context Sensitive operations.

. Insert a synchronization point into the test scpipt at the exact point that the problem occuts.A synchronization point tells WinRunner to pause the test run in order to wait for a specified response in the application.

19) How to change synchronization options?
In Settings / Options click the run tab- Increase the timeout seconds. Or Create wait bitmap option.

20) What is GUI Checkpoint?
A GUI checkpoint examines the bahavior of object's properties

21) What is a checklist?
A checklist contains information about GUI and the selected properties to check.

22) What are the prerequisites for running a test?
a) Make sure that the application under test is Open on the desktop.
b) Check the verity mode
c) Choose run from top
d) Run the test
e) Review the results.

23) When a bitmap check is failed?
When the screen settings are changed.

24) How to add functions in WinRunner?
You can quickly add these functions to a test script using WinRunner's visual Programming tool, the Functiong Genetator.
The Function Generator enables you to add TSL Functions in two ways:
a) You can point to a GUI object and let Win Runner "suggest" an appropriate Function. You can then insert this function into the test script.
b) You can select a function from a list. Functions are presented both by category and alphabetically

25) What is tl_step?
In most cases when you run a test, WinRunner reports an overall test result of Pass or fail. By adding tl_step statements to your test script. You can determine whether a perticular operation within the test passed of failled, and send a Message to the report.

WinRunner Interview Questions

How you used WinRunner in your project? - Yes, I have been using WinRunner for creating automated scripts for GUI, functional and regression testing of the AUT.
Explain WinRunner testing process? - WinRunner testing process involves six main stages
Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.
Debug Test: run tests in Debug mode to make sure they run smoothly
Run Tests: run tests in Verify mode to test your application.
View Results: determines the success or failure of the tests.
Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.
What is contained in the GUI map? - WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description. There are 2 types of GUI Map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
How does WinRunner recognize objects on the application? - WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.
Have you created test scripts and what is contained in the test scripts? - Yes I have created test scripts. It contains the statement in Mercury Interactive’s Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.
How does WinRunner evaluate test results? - Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.
Have you performed debugging of the scripts? - Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.
How do you run your test scripts? - We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.
How do you analyze results and report the defects? - Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.
What is the use of Test Director software? - TestDirector is Mercury Interactive’s software test management tool. It helps quality assurance personnel plan and organize the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.
Have you integrated your automated scripts from TestDirector? - When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
What are the different modes of recording? - There are two type of recording in WinRunner. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.
What is the purpose of loading WinRunner Add-Ins? - Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.
What are the reasons that WinRunner fails to identify an object on the GUI? - WinRunner fails to identify an object in a GUI due to various reasons. The object is not a standard windows object. If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.
What is meant by the logical name of the object? - An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.
If the object does not have a name then what will be the logical name? - If the object does not have a name then the logical name could be the attached text.
What is the different between GUI map and GUI map files? - The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created. GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.
How do you view the contents of the GUI map? - GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description. When you create GUI map do you record all the objects of specific objects? - If we are learning a window then WinRunner automatically learns all the objects in the window else we will we identifying those object, which are to be learned in a window, since we will be working with only those objects while creating scripts.

Load Runner Q & A Part 1

1.Where the LoadRunner will be exactly applicable?

Its mainly applicable for testing the performance of the client and server based applications

2.How the LoadRunner will test the application?

LoadRunner enables us to test our system under controlled and peak load conditions. To generate load LoadRunner runs thousands of virtual users that are distributed over a network. Using a minimum of hardware resources,these virtual users provide consistent,repeatable,and measurable load to exercise our client and server system just as real users would.

3.How to evaluate the performance of a system?

LoadRunner's in-depth reports and graph provide the information that we need to evaluate the performance of our client and server system

4.What are all the compatible platforms which will be used to execute the LoadRunner scripts?

Windows,UNIX

5.What are all the parameters LoadRunner will mainly test?

To load our client and server system, LoadRunner emulates an environment where multiple users work concurrently,while the client and server system is under load, LoadRunner accurately measures and analyze the system performance,and its functionality

6.What kind of applications which will be mainly focused by the performance testing?

Modern client and server architectures are complex. While they provide an unprecedented degree of power and flexibility,these systems are difficult to test. Whereas single user testing focuses primarily on functionality and the user interface of single application,client and server testing focuses on performance and reliability of an entire client and server system.

7.What are the limitations of manual load testing?

? It is expensive,requiring large amount of both personnel and machinery

? It is complicated,especially coordinating and synchronizing multiple users

? It involves a high degree of organization

? The repeatability of the manual tests is limited

8.What are all the main features of LoadRunner?

? LoadRunner reduces the personnel requirements

? LoadRunner reduces the hardware requirements

? The controlling will be accomplished effectively by the controller

? Because LoadRunner tests are fully automated,we can easily repeat them as many times we need

9.What is the purpose of LoadRunner scenarios?

Using LoadRunner,we divide our client and server performance requirements into scenarios. A scenario defines

the events that occur during each testing session.

10.What sort of things will be replaced in scenarios?

In the scenario, LoadRunner replaces human users with virtual users or Vusers. When we run a scenario, Vuser emulate the actions of human users-submitting input into the server.

Load Runner Q & A Part 2

11.What is load testing?

Testing of application for simultaneous users

12.What does vuser_init action contains?

Login procedures

13.What is the main aim of load testing?

To calculate the response time

14.What the Vuser script will do while running the scenario?

The actions that a Vuser performs during the scenario are described in a Vuser script. When we run a scenario,each Vuser executes a Vuser script. The Vuser script include functions that measure and record the performance of the server during the scenario.

15.What is Transaction time?

To measure the performance of the server,we define transactions. Transactions measure the time that it takes for the server to respond to tasks submitted by Vuser.

16.What is Rendezvous points?

We can insert Rendezvous points in to Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct multiple Vuser to perform tasks at exactly the same time.

17.What is controller?

LoadRunner controller is used to manage and maintain our scenarios. Using the controller ,we can control all the Vusers in a scenario from a single work station.

18.What is Hosts?

The host is the machine that executes the Vuser script,enabling the Vuser to emulate the actions of a human user.

19.What is mean by Rendezvous points?

A rendezvous point creates intense user load on the server and enables LoadRunner to measure server performance under load

20.What is the need for doing load testing?

The factors are: Minimal infrastructure,Reliable,Repeatable,Programmable,Comprehensive,Reusable

21.How to create Vuser Groups in loadrunner?

A scenario consists of groups of Vusers which emulate human user interacting with your application. When you run a scenario, the Vusers generate load on the server, and LoadRunner monitors the server and transaction performance

22.Why should we automate the performance testing?

Its a discipline that leverages products,people and processes to reduce the risk of application,upgrade or patch deployment. It is about applying production work loads to pre-deployment systems while simultaneously measuring system performance and end-user experience.

23.What are all the things will be considered while doing performance testing?

? Does the application respond quickly enough for the intended users?

? Will the application handle the expected user load and beyond?

? Will the application handle the number of transactions required by the business?

? Is the application stable under expected and unexpected user loads?

? Are we sure that users will have a positive experience on go-live day?

24. What are the LoadRunner components?

? Virtual User Generator

? Controller

? Load Generators

? Analysis

? Launcher

25. What is the LoadRunner testing process?

? Plan load test

? Create Vuser Scripts

? Define Scenario

? Run Scenario

? Analyze results

26.What is remote command launcher?

The remote command launcher enables the controller to start applications on the host machine