Explore topic-wise InterviewSolutions in .

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

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

Through SCENARIO WIZARD we can CREATE a NEW scenario.

Through scenario wizard we can create a new scenario.

LOADRUNNER SAVE the INFORMATION in a SCENARIO FILES.

LoadRunner save the information in a scenario files.

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

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

TITLE BAR(NAME of the SCENARION presently working). Menu bar(selecting the VARIOUS command). Tool bar. Status bar.

Title bar(name of the scenarion presently working). Menu bar(selecting the various command). Tool bar. Status bar.

Rendezvous POINT insert in to the SCRIPT to CALCULATE the PEAK load of the server.

Syntax: lr-rendezvous ("rendezvous name").

Rendezvous point insert in to the script to calculate the peak load of the server.

Syntax: lr-rendezvous ("rendezvous name").

While editing the script we have to INSERTING the transaction POINT and RENDEZVOUS point.

While editing the script we have to inserting the transaction point and rendezvous point.

By RECORDING the ACTIVITY between CLIENT and SERVER.

By recording the activity between client and server.

RECORD a LOG off in to the SERVER (VUSER STOPED).

Record a log off in to the server (vuser stoped).

RECORD the CLIENT ACTIVITY .

Record the client activity .

RECORD a LOG in to the server(vuser INITIALIZE LOADED).

Record a log in to the server(vuser initialize loaded).

VUGEN CONTAIN the 3 SECTION .
1-vuser-init
2-action.
3-vuser-end.

Vugen contain the 3 section .
1-vuser-init
2-action.
3-vuser-end.

OBTAIN the INFORMATION about the TYPE of VUSER.

Obtain the information about the type of vuser.

OBTAIN the INFORMATION about VUSER RUNNING in a SCENARIO .

obtain the information about vuser running in a scenario .

1-LR FUNCTION.(VUSER function)
2- PROTOCOL function.

1-LR Function.(vuser function)
2- protocol function.

To VERIFY that the SCRIPT RUNS CORRECTLY.

To verify that the script runs correctly.

Run-time-setting INCLUDE loop.log and TIMING INFORMATION.

Run-time-setting include loop.log and timing information.

By ADDING control-flow, structure, by INSERTING TRANSACTION point and rendezvous point, adding FUNCTIONS.

By adding control-flow, structure, by inserting transaction point and rendezvous point, adding functions.

3 SECTION ,written in code that assemble in C, SQL call to the DATABASE, written in TSL(test SCRIPT LANGUAGE).

3 section ,written in code that assemble in C, SQL call to the database, written in TSL(test script language).

DEVELOPING the database vuser SCRIPT EITHER by recording with LoadRunner vuser script generator (VUGEN) or by using LoadRunner vuser script template.

Developing the database vuser script either by recording with LoadRunner vuser script generator (VuGen) or by using LoadRunner vuser script template.

X-runner and VX-runner for X-Windows APPLICATION.

X-runner and VX-runner for X-Windows application.

WINRUNNER USED for MS-Window APPLICATION .

WinRunner used for MS-Window application .

GUI VUSER operate graphical USER INTERFACE application and it can run in either the MS-Windows / X-Windows ENVIRONMENT .

GUI vuser operate graphical user interface application and it can run in either the MS-Windows / X-Windows environment .

There are SEVERAL type of vuser(GUI ,Database ,RTE(terminal EMULATOR), SAP, DCOME, People soft, JAVA, BAAN)

There are several type of vuser(GUI ,Database ,RTE(terminal emulator), SAP, DCOME, People soft, java, Baan)

Rcl ENABLES the CONTROLLER to start the application on the Host machine .

Rcl enables the controller to start the application on the Host machine .

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.

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.

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.

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.

Creating VUSER script for EMULATE the action that VIRTUAL user Perform during the SCENARIO execution.

Creating vuser script for emulate the action that virtual user Perform during the scenario execution.

Define the performance testing REQUIREMENTS for example no. of concurrent users, TYPICAL business processes and required response TIME.

Define the performance testing requirements for example no. of concurrent users, typical business processes and required response time.

HOST is MACHINE which EXECUTE the VUSER SCRIPT.

Host is machine which execute the vuser script.

When multiple vuser to perform tasks at EXACTLY the same TIME then INSERT the RENDEZVOUS point to emulate the peak LOAD on the server.

When multiple vuser to perform tasks at exactly the same time then insert the rendezvous point to emulate the peak load on the server.

To EMULATE PEAK LOAD on the SERVER.

To emulate peak load on the server.

TRANSACTION measure the TIME, which takes for the SERVER to RESPOND to task SUBMITTED by the vuser.

Transaction measure the time, which takes for the server to respond to task submitted by the vuser.

The vuser SCRIPT INCLUDES the FUNCTION that measure and RECORD the PERFORMANCE of the server during the scenario.

The vuser script includes the function that measure and record the performance of the server during the scenario.

While RUN a SCENARION every VUSER EXECUTE a script that script known as vuser script .

While run a scenarion every vuser execute a script that script known as vuser script .

LOADRUNNER REPLACE the HUMAN USER with VUSER.

LoadRunner replace the human user with vuser.

A scenario DEFINES the EVENTS that occur during is testing SESSION. Exam (deposit CASH, withdraw money…).

A scenario defines the events that occur during is testing session. Exam (deposit cash, withdraw money…).

PARAMETERIZATION is generally done to test with MULTIPLE set of DATA or records.

Parameterization is generally done to test with multiple set of data or records.

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 start 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 s 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);
}

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 start 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 s 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);
}

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.

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.

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.

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.

Monitor system bottlenecks during a TEST run and capture and display the PERFORMANCE data from EVERY SERVER or component.

Monitor system bottlenecks during a test run and capture and display the performance data from every server or component.

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.

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.

It will END the TRANSACTION. SYNTAX. Lr-end-transaction("transaction NAME", LR-AUTO).

It will end the transaction. Syntax. Lr-end-transaction("transaction name", LR-AUTO).

It will START the TRANSACTION on the SCRIPT. SYNTAX. Lr-start-transaction("transaction NAME").

It will start the transaction on the script. Syntax. Lr-start-transaction("transaction name").

Data base vuser do not operate CLIENT APPLICATION. Using LoadRunner API function the DATABASE vuser can access the data from the server.

Data base vuser do not operate client application. Using LoadRunner API function the database vuser can access the data from the server.

CONTROLLER INSTRUCT the remote command LUNCHER to LUNCH the Agent .

Controller instruct the remote command luncher to lunch the Agent .

AGENT is INTERFACE between HOST MACHINE and CONTROLLER.

Agent is interface between host machine and controller.

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.

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.

Controller is manage and MAINTAIN the SCENARIO. using controller you CONTROL all the VUSER in single WORK station .

Controller is manage and maintain the scenario. using controller you control all the vuser in single work station .