Dear Readers, Welcome to LoadRunner Interview Questions and Answers have been designed specially to get you acquainted with the nature of questions you may encounter during your Job interview for the subject of LoadRunner. These LoadRunner Questions are very important for campus placement test and job interviews. As per my experience good interviewers hardly plan to ask any particular questions during your Job interview and these model questions are asked in the online technical test and interview of many IT companies.
Industry standard protocols for example HTTP and ODBC are explicitly supported by LoadRunner. Furthermore any protocol that communicates over a windows socket can be supported.
In addition to knowing the tool :
- Management aspects of Load Testing, Planning being paramount
- Requirements gathering, Profile/Mix, SLA, Acceptance Criteria....
- an general understanding of the protocol you are working with, developers can be unhelpful
- a basic understanding of C programming
- know that you WILL be working with diminishing timescales and you are really at the END of the lifecycle
- as a result of the above you may have to work unsociable hours including weekends
- Managers and other "Powes that be" - "Box tickers" will not understand your plight
- You need to be able to communicate effectively at all levels with different departments from Business to Dev to Sys Test
- voice your problems as soon as possible - Planning Planning
- Fail to Plan - Plan to FAIL
Monitor system bottlenecks during a test run and capture and display the performance data from every server or component.
Unlimited, No dead end.,
Depends on system response. That too inturn depends on various factors like entire system configuration etc. If system bottle necks observes in very begining or minimum no of Vusers no further addition of vusers will be considered unless observed bottleneck is resolved.
ApplicationComponents used are client, database or additionally business application server.)
Web Server works on and through LAN,WAN,or www connection.
Application Server components are client, business server and database server without use of www.but through Protocols like FTP.
This function is developed to usein Mercury LoadRunner peformance tool. This main use of this functions to return the current system time at any given point of time while LoadRunner script is running.This functiona can be used to report transaction times , script starti time and end time.
long get_secs_since_midnight(void)
{
char * curr_hr; /* pointer to a parameter with current clock hr */
char * curr_min; /* pointer to a parameter with current clock min*/
char * curr_sec; /* pointer to a parameter with current clock sec */
long current_time, /* current number of seconds since midnight */
hr_secs, /* current hour converted to secs */
min_secs, /* current minutes converted to secs */
secs_secs; /* current number of seconds */
curr_hr = lr_eval_string("{current_hr}>");
curr_min = lr_eval_string("{current_min}");
curr_sec = lr_eval_string("{current_sec}");
hr_secs = (atoi(curr_hr)) * 60 * 60;
min_secs = (atoi(curr_min)) * 60;
secs_secs = atoi(curr_sec);
current_time = hr_secs + min_secs + secs_secs;
return(current_time);
}
Parameterization is generally done to test with multiple set of data or records.
LoadRunner accurately measure and analysis the system performance and its functionality.
When multiple users work concurrently.
1-loadrunner automatically records the performance of the client/server during test. 2-loadrunner checks where performance delays occur network/client delays. 3-loadrunner monitor the network and server resource to help the improve performance.
A scenario defines the events that occur during is testing session. Exam (deposit cash, withdraw money…).
LoadRunner replace the human user with vuser.
While run a scenarion every vuser execute a script that script known as vuser script .
The vuser script includes the function that measure and record the performance of the server during the scenario.
Transaction measure the time, which takes for the server to respond to task submitted by the vuser.
To emulate peak load on the server.
17. When the rendezvous point is insert.
When multiple vuser to perform tasks at exactly the same time then insert the rendezvous point to emulate the peak load on the server.
Controller is manage and maintain the scenario. using controller you control all the vuser in single work station .
Host is machine which execute the vuser script.
There are 5 steps.
1-planning the test.
2-creating the vuser script.
3-creating the scenario.
4- running the scenario.
5-analysis the test result.
Define the performance testing requirements for example no. of concurrent users, typical business processes and required response time.
Creating vuser script for emulate the action that virtual user Perform during the scenario execution.
There are 5 steps for developing a vuser script.
1-recording the vuser script .
2-edit the vuser script.
3-runtime setting .
4-run the vuser script in stand-alone mode.
5-incorporate the vuser script into a LoadRunner scenario.
We have to install LoadRunner controller to the host . Then we include list of host(where vuser script execute) then list of vuser script (where vuser run) and then list of vuser that run during the scenario.
Rcl enables the controller to start the application on the Host machine .
Agent is interface between host machine and controller.
Controller instruct the remote command luncher to lunch the Agent .
There are several type of vuser(GUI ,Database ,RTE(terminal emulator), SAP, DCOME, People soft, java, Baan)
GUI vuser operate graphical user interface application and it can run in either the MS-Windows / X-Windows environment .
WinRunner used for MS-Window application .
X-runner and VX-runner for X-Windows application.
Data base vuser do not operate client application. Using LoadRunner API function the database vuser can access the data from the server.
Developing the database vuser script either by recording with LoadRunner vuser script generator (VuGen) or by using LoadRunner vuser script template.
3 section ,written in code that assemble in C, SQL call to the database, written in TSL(test script language).
By adding control-flow, structure, by inserting transaction point and rendezvous point, adding functions
Run-time-setting include loop.log and timing information.
To verify that the script runs correctly.
1-LR Function.(vuser function) 2- protocol function.
obtain the information about vuser running in a scenario .
Obtain the information about the type of vuser.
Vugen contain the 3 section .
1-vuser-init
2-action.
3-vuser-end.
Record a log in to the server(vuser initialize loaded).
Record the client activity .
Record a log off in to the server (vuser stoped).
By recording the activity between client and server.
While editing the script we have to inserting the transaction point and rendezvous point.
It will start the transaction on the script. Syntax. Lr-start-transaction("transaction name").
It will end the transaction. Syntax. Lr-end-transaction("transaction name", LR-AUTO).
Rendezvous point insert in to the script to calculate the peak load of the server. Syntax. lr-rendezvous("rendezvous name").
Title bar(name of the scenarion presently working). Menu bar(selecting the various command). Tool bar. Status bar.
1-host windows(list of machine).
2-script windows(list of all the vuser script)
3-rendezvous windows.
4-transaction windows(display all the transaction) .
5-output window( display error and notification message).
LoadRunner save the information in a scenario files.
Through scenario wizard we can create a new scenario.
We can filter the information display only those items that meet the selected criteria(filter box) .exam you can filter vuser only those who are in ready state. Sorting - we can sort all the vuser in the vuser list. In order to their vuser ID(1,2,3,4,5,6,7,8,9).
1-the status of the host.
2-the platform type of the host(windows/unix).
3-details of the scenario.
1-install remote command luncher on every machine.
2-add the name of the host to the host lists.
3-set attributes for each host.
4-select which hosts will take part in the scenario.
1-the maximum number of vuser that host can run.
2-the initialization quota .
3-the location of the WinRunner configuration file.
4. the location of the file during run-time.
We can modify the maximum number of vuser according to the (available resource , the needs of your scenario, LoadRunner license agreements).
Capabilities of the host that at a time how many vuser Are initialize .
Wrun.ini.
Instruct the vuser to use the WinRunner configuration file.
Instruct the vuser to use hosts WinRunner configuration file.
Use WinRunner configuration file that is in a specific location on the network.
In temporally in the local drive of each host.
It contain all the vuser script that vuser can run.
1-name of the vuser script .
2-the type of the vuser.
3-the location(path).
4-command line option.
Using vuser script information dialog box.
To check the response time of the client/server system under load.
If a multiple vuser to perform a tasks at exactly the same time.
1-The controller check the scenario configuration information.
2-then next it invoke the application that you select to run with the scenario .
3- then transform each script to its related hosts, when the vuser are ready they start execution.
Open an existing scenario .
Configure the scenario.
Set the result directory.
Run the scenario.
The vuser status change from DOWN to PENDING to INITILIZAING to READY. If vuser fails to initialize , the vuser status changes to ERROR.
It changes the status of the vuser from RUNNING TO PAUSE.
It displays the number of the vuser that execute vuser script during each second of the scenario run. Only running and rendez state are include.(loading, ready and pause are not displayed).
Each report viewer contain the report header and report viewer tool bar.
It display general scenario information and it contain the information like (title, scenario, result start time, end time and duration).
It indicate when vuser were released from rendezvous point and how many vuser are released from each point.it help the transaction performance time .
It display the number of complited , successful transaction perform during each second of scenario run.
The percentage of transaction that were performed within a given time range.
Display the average time taken to perform transaction during each second of the scenario run.