Ans: LoadRunner works by creating virtual users who take the place of real users operating client software, such as sending requests using the HTTP protocol to IIS or Apache web servers. Requests from many virtual user clients are generated by Load Generators in order to create a load on various servers under test these load generator agents are started and stopped by Mercury's Controller program. The Controller controls load test runs based on Scenarios invoking compiled Scripts and associated Run-time Settings. Scripts are crafted using Mercury's "Virtual user script Generator" (named "V U Gen"), It generates C-language script code to be executed by virtual users by capturing network traffic between Internet application clients and servers. With Java clients, VuGen captures calls by hooking within the client JVM. During runs, the status of each machine is monitored by the Controller. At the end of each run, the Controller combines its monitoring logs with logs obtained from load generators, and makes them available to the "Analysis" program, which can then create run result reports and graphs for Microsoft Word, Crystal Reports, or an HTML webpage browser.
Each HTML report page generated by Analysis includes a link to results in a text file which Microsoft Excel can open to perform additional analysis. Errors during each run are stored in a database file which can be read by Microsoft Access.
Ans: Load runner is used to test applications when load sustaining is critical for our project and the tool/application developed is expected to work under heavy loads. In all cases, load testing manually is not possible.
Ans: The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online.
Ans:
Ans: The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online. 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.
Ans: Controller is manage and maintain the scenario. using controller you control all the vuser in single work station .
Ans: There are 5 steps.
Ans: 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.
Ans: Agent is interface between host machine and controller.
Ans: Data base vuser do not operate client application. Using LoadRunne
r API function the database vuser can access the data from the server.
Ans: 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.
Ans: 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.
Ans: 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.
Ans: 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.
Ans: Monitor system bottlenecks during a test run and capture and display the performance data from every server or component.
Ans: 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.
Ans: Parameterization is generally done to test with multiple set of data or records.
Ans: When multiple vuser to perform tasks at exactly the same time then insert the rendezvous point to emulate the peak load on the server.
Ans: 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.
Ans: 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.
Q21. Where do you set automatic correlation options?
Ans: 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.
Ans: Host is machine which execute the vuser script.
Ans: There are 5 steps for developing a vuser script.
Ans: 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.
Ans: Rcl enables the controller to start the application on the Host machine .
Ans: There are several type of vuser(GUI ,Database ,RTE(terminal emulator), SAP, DCOME, People soft, java, Baan)
Ans: GUI vuser operate graphical user interface application and it can run in either the MS-Windows / X-Windows environment .
Ans: 3 section ,written in code that assemble in C, SQL call to the database, written in TSL(test script language).
Ans: By adding control-flow, structure, by inserting transaction point and rendezvous point, adding functions.
Ans: Run-time-setting include loop.log and timing information.
Ans: To verify that the script runs correctly.
Ans: LoadRunner script code obtained from recording in the ANSI C language syntax, represented by icons in icon view until you click Script View.
Ans: Vugen contain the 3 section .
Ans: Record a log in to the server(vuser initialize loaded).
Ans: Record a log off in to the server (vuser stoped).
Ans: Title bar(name of the scenarion presently working). Menu bar(selecting the various command). Tool bar. Status bar.
Ans:
Ans: 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*)
Ans: The Run Time Settings that we make are:
Pacing - It has iteration count.
Log - Under this we have Disable Logging Standard Log and
Extended Think Time - In think time we have two options like Ignore think time and Replay think time.
General - Under general tab we can set the vusers as process or as multithreading and whether each step as a transaction.
Ans: 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.
Ans: 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.