Thursday, 26 June 2014

LOADRUNNER INTERVIEW QUESTIONS





  1. What protocols does Load Runner support?

    Industry standard protocols for example HTTP and ODBC are explicitly supported by Load Runner. Furthermore any protocol that communicates over a windows socket can be supported.

    2. What do I need to know to do load testing in addition to knowing how to use the Load Runner tool?

    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 life cycle
    - 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

    3. What can I monitor with Load Runner?

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

    4. How many users can I emulate with Load Runner on a PC?

    Unlimited, No dead end.,
    Depends on system response. That too intern depends on various factors like entire system configuration etc. If system bottle necks observes in very beginning or minimum no of V users no further addition of v users will be considered unless observed bottleneck is resolved.

    5. What are the V user components in Load Runner?

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

    6. Load Runner Function - How to get current system time

    This function is developed to use in Mercury Load Runner performance tool. This main use of this functions to return the current system time at any given point of time while Load Runner script is running.This functions can be used to report transaction times , script strati 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);
    }

    7. What are the reasons why parametrization is necessary when load testing the Web server and the database server.

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

    8. what is Load Runner.

      Load Runner accurately measure and analysis the system performance and its functionality.

    9. When Load Runner is used.

    When multiple users work concurrently.
10.What is the advantage of using Load Runner.

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.

11. What is scenario?

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

12. what is the v user in the scenario.

  Load Runner replace the human user with v user.

13. What is v user script?

While run a scenario every v user execute a script that script known as v user script .

14. What the v user script contain.

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

15. What is transaction?

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

16. What is rendezvous point.

To emulate peak load on the server.

17. When the rendezvous point is insert.

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

18. What is Load Runner controller?

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

19. what is Host.

Host is machine which execute the v user script.

20. what are the Load Runner testing process.

There are 5 steps.
1-planning the test.
2-creating the v user script.
3-creating the scenario.
4- running the scenario.
5-analysis the test result.

21. what is planning for the test.

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

22. what do you mean by creating v user script.

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

23. what are the process for developing a v user script.

There are 5 steps for developing a v user script.
1-recording the v user script .
2-edit the v user script.
3-runtime setting .
4-run the v user script in stand-alone mode.
5-incorporate the v user script into a Load Runner scenario.

24. how to create a scenario?

We have to install Load Runner controller to the host . Then we include list of host(where v user script execute) then list of v user script (where v user run) and then list of v user that run during the scenario.

25. what do you mean by Remote Command Launcher(R CL).

  R cl enables the controller to start the application on the Host machine .

26. what is Load Runner Agent.

Agent is interface between host machine and controller.

27. how you load a Load Runner Agent.

Controller instruct the remote command launcher to lunch the Agent .

28. how many types of v user are available.

There are several type of v user(GUI ,Database ,RTE(terminal emulator), SAP, D COME, People soft, java)

29. what is GUI v user and on which platform it will run.

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

31. what is MS-windows.

  Win Runner used for MS-Window application .

32. what is X-Windows.

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

33. What is Load Runner API function.

Data base v user do not operate client application. Using Load Runner API function the database v user can access the data from the server.

34. how you develop the database v user script.

Developing the database v user script either by recording with Load Runner v user script generator (V uGen) or by using Load Runner v user script template.

35. how many section database v user script have.

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

36. how you enhance the basic script.

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

37. what is run-time-setting.

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

38. what is stand-alone mode.

To verify that the script runs correctly.

39. what type of function generate and insert by the vugen to the script when you record a script.

1-LR Function.(v user function) 2- protocol function.

40. what is LR-function.

obtain the information about v user running in a scenario .

41. what is protocol function.

Obtain the information about the type of v user.

42. what are the section contain by the vugen while creating a v user script.

V u gen contain the 3 section .
1-vuser-init
2-action.
3-vuser-end.

43. what is user-innit section.

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

44. what is action section.

Record the client activity .

45. what is v user-end section.

Record a log off in to the server (v user stored).

46. how vugen create a v user script.

By recording the activity between client and server.

47. How you edit the script.
While editing the script we have to inserting the transaction point and rendezvous point.


48. what is the Load Runner start-transaction and its syntax.

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

49. what is the Load Runner end transaction and its syntax.

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

50. where you insert the rendezvous point.

Rendezvous point insert in to the script to calculate the peak load of the server. Syntax. l-rendezvous("rendezvous name").

51. what are the element in the Load Runner controller.

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

52. what are the 5 icons appear in the button of the controller windows.

1-host windows(list of machine).
2-script windows(list of all the v user script)
3-rendezvous windows.
4-transaction windows(display all the transaction) .
5-output window( display error and notification message).

53. what is .lrs.

  Load Runner save the information in a scenario files.

54. what is scenario wizard.

Through scenario wizard we can create a new scenario.

55. what is filtering and sorting.

We can filter the information display only those items that meet the selected criteria(filter box) .exam you can filter v user only those who are in ready state. Sorting - we can sort all the v user in the V user list. In order to their v user ID(1,2,3,4,5,6,7,8,9).

56. what are the information crating for each host.

1-the status of the host.
2-the platform type of the host(windows/UNIX).
3-details of the scenario.


57. how to create a host list for a scenario.

1-install remote command launcher 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.

59. what the host attributes determine.

1-the maximum number of v user that host can run.
2-the initialization quota .
3-the location of the Win Runner configuration file.
4. the location of the file during run-time.

60. how you set maximum number of v user that a host can run.

We can modify the maximum number of v user according to the (available resource , the needs of your scenario, Load Runner license agreements).

61. what do you mean by initialization of quota.

Capabilities of the host that at a time how many v user Are initialize .

62. when the LoadRunner controller open the Win Runner file then what is the location of the winner configuration file.

W run.ini.

63. what is scenario default.

Instruct the v user to use the Win Runner configuration file.

64. what is local configuration file.

Instruct the v user to use hosts Win-runner configuration file.

65. what do you mean by path.

Use Win Runner configuration file that is in a specific location on the network.

66. during run time where the hosts saves the files.

In temporally in the local drive of each host.


67. what is script list.

It contain all the v user script that v user can run.

68. what are the information contain by script windows for each script in the list.

1-name of the v user script .
2-the type of the v user.
3-the location(path).
4-command line option.

69. How to modify the script.

Using v user script information dialog box.

70. what is the purpose of running the scenario.

To check the response time of the client/server system under load.

71. why we insert the rendezvous point while running the scenario.

If a multiple v user to perform a tasks at exactly the same time.

72. when a scenario run exactly what happened.

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 v user are ready they start execution.

73. how to run a scenario.

Open an existing scenario .
Configure the scenario.
Set the result directory.
Run the scenario.
74. when you initialize the v user what happen.

The v user status change from DOWN to PENDING to INITIALIZING to READY. If v user fails to initialize , the v user status changes to ERROR.

75. what is pause command.

It changes the status of the v user from RUNNING TO PAUSE.

76. what is running virtual user graph.

It displays the number of the v user that execute v user script during each second of the scenario run. Only running and render state are include.(loading, ready and pause are not displayed).

77. What is report viewer?

Each report viewer contain the report header and report viewer tool bar.

78. what is report header and what are the information contains.

It display general scenario information and it contain the information like (title, scenario, result start time, end time and duration).

79. what is rendezvous graph.

It indicate when v user were released from rendezvous point and how many v user are released from each point.it help the transaction performance time .

80. what is transaction per second graph(pass).

It display the number of complied , successful transaction perform during each second of scenario run.

81. what in percentile graph.

The percentage of transaction that were performed within a given time range.

82. what is transaction performance graph.
Display the average time taken to perform transaction during each second of the scenario run.

83. What are all the types of correlation?
Manual & Automatic Co-relation
Manual correlation - Correlation is used to obtain data which are unique for each run of the script and which are generated by 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.


No comments:

Post a Comment