Introdu 1 ction to HP Load Runner Getting Familiar with Load Runner

1. Introdu1ction to HP Load Runner Getting Familiar with Load Runner

2. Getting Familiar with LoadRunner Why LoadRunner System Requirements LoadRunner Installation LoadRunner Terminology LoadRunner Components How LoadRunner Works

3. Why LoadRunner An industry-leading performance and load testing product by Hewlett-Packard (since it acquired Mercury Interactive in November 2006). LoadRunner reduces the personnel requirements by replacing human users with virtual users or Vusers. These Vusers emulate the behavior of real users — operating real applications. Because numerous Vusers can run on a single computer, LoadRunner reduces the hardware requirements. The LoadRunner Controller allows you to easily and effectively control all the Vusers — from a single point of control. LoadRunner monitors the application performance online, enabling you to fine-tune your system during test execution.

4. Why LoadRunner LoadRunner automatically records the performance of the application during a test. You can choose from a wide variety of graphs and reports to view the performance data. LoadRunner checks where performance delays occur: network or client delays, CPU performance, I/O delays, database locking, or other issues at the database server. LoadRunner monitors the network and server resources to help you improve performance. Because LoadRunner tests are fully automated, you can easily repeat them as often as you need.

5. System Requirements- Controller, VuGen and Analysis System Requirements Processor: CPU Type: Intel Core, Pentium, AMD or compatible Speed: 1 GHz minimum. 2 GHz or higher recommended Intel Hyper-Threading technology is not supported. Operating System: The following 32-bit Windows operating systems are supported: Windows Vista SP1 Windows XP Professional SP2 or SP3 Windows Server 2003 Standard Edition/Enterprise Edition SP2 Windows Server 2003 Standard Edition/Enterprise Edition R2 SP2 RAM: Minimum: 512 MB Recommended: 1 GB or higher

6. System Requirements- Controller, VuGen and Analysis System Requirements Screen Resolution: Minimum: 1024 x 768 Browser Microsoft Internet Explorer 6.0 SP1 or SP2 Microsoft Internet Explorer 7.0 Available Hard Disk Space: Minimum 1.5 GB

7. System Requirements- Load Generator Processor: CPU Type: Intel Core, Pentium, AMD or compatible Speed: 1 GHz minimum. 2 GHz or higher recommended Intel Hyper-Threading technology is not supported. Operating System: The following 32-bit Windows operating systems are supported: Windows Vista SP1 Windows XP Professional SP2 or SP3 Windows Server 2003 Standard Edition/Enterprise Edition SP2 Windows Server 2003 Standard Edition/Enterprise Edition R2 SP2 RAM: Minimum: 1 GB Memory depends on protocol type and system under test and can vary greatly.

8. System Requirements- Load Generator Browser Microsoft Internet Explorer 6.0 SP1 or SP2 Microsoft Internet Explorer 7.0 Available Hard Disk Space: Minimum 1 GB

9. LoadRunner Installation Run the setup.exe file in the root directory of the installation disk. The LoadRunner Setup program begins and displays the installation menu page.

10. Load Runner Installation Load Runner Full Setup. Provides the option to install the main Load Runner features and components including the Controller, the VuGen, Analysis, and the Load Generator. Load Generator. Installs the components needed for running virtual users to generate load, and the MI Listener.

11. Load Runner Installation If necessary, install prerequisite software. Click OK and follow the on-screen instructions to install the listed software before continuing with the Load Runner installation. If you click Cancel, the installer will exit because Load Runner cannot be installed without the prerequisite software.

12. Load Runner Installation Review the License agreement. If the terms of the license agreement are acceptable to you, choose I Agree. Click Next to proceed.

13. Load Runner Installation Register the Load Runner Installation on your computer. In the Customer Information page, enter your name and organization name. Click Next to proceed.

14. Load Runner Installation Select a setup type. (Only for Load Runner Full Setup) In the Setup Type page, choose between a Complete or Custom setup. Complete. Installs the complete set of Load Runner features. Most users should select this option. Custom. Installs only those Load Runner features that you choose to install. Click Next to proceed.

15. Load Runner Installation- Custom Options Select features to install. (Only for Custom setup) If you chose to perform a Custom installation of Load Runner, select the Load Runner features that you want to install. By default, all the features are selected for installation.

16. Load Runner Installation Select an installation folder. Accept the proposed folder for the installation or browse to an alternate folder. Click Disk Cost to check the disk space for each drive. The dialog box displays the size, available space, and required space for each disk. Click OK to close the Disk Cost dialog box. Click Next to proceed.

17. Load Runner Installation Complete the installation process. When the installation is complete, a wizard page opens, confirming successful installation.

18. Load Runner Installation Finish the Installation. Click Finish. The Load Runner Launcher opens displaying the Load Runner License Information Dialog Box. The Load Runner installation is now complete. To start Load Runner, select start > Programs > Load Runner > Load Runner. Select the application that you want to run from the Load Runner launcher window.

19. Load Runner Installation- Uninstall, Repair, Modify To uninstall Load Runner, use the Windows Add/Remove Programs utility. Alternatively, you can run the setup.exe file located in the root directory of the Load Runner installation disk and select the Remove option in the Setup Wizard. To repair Load Runner, run the setup.exe file located in the root directory of the Load Runner installation disk and select the Repair option in the Setup Wizard If you want to install additional Load Runner features after you have completed the installation, run the setup.exe file located in the root directory of the Load Runner installation disk, select the Modify option in the Setup Wizard, and then select the additional features from the list of available features.

20. Load Runner Terminology Scenarios: Using Load Runner, application performance testing requirements are divided into scenarios. A scenario defines the events that occur during each testing sessions. For example, a scenario defines and controls the number of users to emulate, the actions that they perform, and the machines on which they run their emulations. Vusers In a scenario, Load Runner replaces human users with virtual users or Vusers. In a scenario, Vusers emulate the actions of human users—submitting input to the server. A scenario can contain tens, hundreds, or even thousands of Vusers.

21. Load Runner Terminology Vuser Scripts The actions that a Vuser performs during the scenario are described in a Vuser script When a scenario is executed, each Vuser executes a Vuser script. Vuser scripts include functions that measure and record the performance of the server during the scenario. Transactions To measure the performance of the server, transactions are defined. Transactions measure the time that it takes for the server to respond to tasks submitted by Vusers.

22. Load Runner Terminology Rendezvous Points Rendezvous points are used into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct multiple Vusers to perform tasks at exactly the same time. For example, to emulate peak load on the bank server, we insert a rendezvous point to instruct 100 Vusers to simultaneously deposit cash into their accounts. Controller Load Runner Controller is used to manage and maintain scenarios. Using the Controller, we can control all the Vusers in a scenario from a single workstation.

23. Load Runner Terminology Hosts When you execute a scenario, the Load Runner Controller distributes each Vuser in the scenario to a host. The host is the machine that executes the Vuser script, enabling the Vuser to emulate the actions of a human user. Performance Analysis Vuser scripts include functions that measure and record system performance during load-testing sessions. During a scenario run, you can monitor the network and server resources. Following a scenario run, you can view performance analysis data in reports and graphs.

24. How Load Runner Works

25. How Load Runner Works Load Runner works by creating virtual users who take the place of real users operating client software sending requests using the HTTP protocol to web servers. Requests from many virtual user clients are generated by "Load Generators" in order to create a load on various servers under test The Controller controls load test runs based on "Scenarios" invoking compiled "Scripts" and associated "Run-time Settings".

26. How Load Runner Works Scripts are crafted using "Virtual user script Generator" (named "VU Gen"), It generates C-language script code to be executed by virtual users by capturing network traffic between Internet application clients and servers. 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.

27. Objectives of Performance Testing Application Response Time How long does it take to complete a task? How Stable is the system under a heavy work load? Reliability Which configuration provides the best performance level? Configuration Sizing At what point does degradation in performance occur? Capacity Planning Is the system stable enough to go into Production? Acceptance What is the cause of degradation in performance? Bottleneck Identification Does the new version of Software adversely affect response time? Regression Product Evaluation

28. Supporting Environments • Application Deployment Solution - The Citrix protocol. • Client/Server - MS SQL, ODBC, Oracle Web Applications 11i, DB2 CLI, Sybase Ctlib, Sybase Dblib, Windows Sockets, and DNS protocols. • Custom - C templates, Visual Basic templates, Java templates, Javascript, and VBScript type scripts. • Distributed Components - COM/DCOM, Corba-Java, and Rmi-Java protocols. • E-Business - FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, and the dual Web/Winsocket protocols. • Enterprise Java Beans -EJB Testing and RMI-Java protocols. • ERP/CRM - Baan, Oracle NCA, PeopleSoft 8, Peoplesoft-Tuxedo, SAP-Web, SAPGUI, SAPGUI/SAP-Web dual, and Siebel (Siebel-DB2 CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols. Contd….

29. App. Servers Database Server Web Servers Clients Internet/Intranet Supporting Environments • Legacy Terminal Emulation (RTE). • Mailing Services Internet Messaging (IMAP), MS Exchange (MAPI), POP3, and SMTP. • Streaming Media Player and RealPlayer protocols. • Wireless i-Mode, VoiceXML, and WAP protocols.

30. Supporting Environments • Platforms • NT, 2000, XP • Sun • HP • IBM • Linux

32. Tuning Controller VuGen LoadRunner Analysis Load Runner Components Contd….

33. Virtual User Generator LoadRunner Controller LoadRunner Analysis The Load Runner Solution Creates Scripts as one Single User. Generates load and collects test results Compiles and displays test results with graphical and statistical tools

34. Components of Load Runner • VuGen (Virtual User Generator) – records Vuser Scripts that emulate the steps of real Users using the application • The Controller is an administrative centre for creating, maintaining, and executing scenarios. Starts and stops load tests, and perform other Administrative tasks Contd….

35. Components of Load Runner • LR Analysisuses the load test results to create graphs and reports that are used to correlate system information and identify both bottlenecks and performance issues. • Tuninghelps you quickly isolate and resolve performance bottlenecks. By adding a centralized tuning console to Load Runner, the Mercury Tuning Module ensures that performance bottlenecks are resolved during testing, and helps you determine the optimized configuration settings for production.

36. How Load Runner Works ?

37. Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Plan Load Test Create Web Virtual Users CreateScenarios RunScenarios AnalyzeSystem Under Load LoadRunner V U G E N LoadRunner C O N T R O L L E R & A N A L Y S I S Load Runner Expert Workflow “The Big Picture” TuneSystem Based on Analysis

38. Plan Load Test Identify Business Critical Scenarios. Scenario means a manual work flow. Ex: Login  Open an Account  Logout. Estimate User Load Performance Testing requirements will give an idea of users load or the number of users using the product. This will determine the load to be used against the product in testing. Work Load: Ex: 100 user Running together. Of this 60 users book a Browse a website. 30 users search a product and 10 users buy the Product.

39. What is Virtual User (Vuser) ? • Virtual users or Vusers emulate the steps of real users. The steps that Vusers perform are recorded in a Vuser Script.

40. What is VuGen (Virtual User Generator) ? • VuGen records Vuser Scripts that emulate the steps of real users using the application • VuGen not only records Vuser scripts, but also runs them. Running scripts from VuGen is useful for debugging • VuGen records sessions on Windows platforms only. However, a recorded Vuser script can run on both Windows and UNIX platform. Cont…

41. Process of Recording Script • Recorda basic script • Enhancethe basic script by adding the control-flow statements and other Mercury API functions into the Script • Configurethe Run-time settings • Verifythat the script runs correctly, run it in stand-alone mode • Integrateinto your test : a Load Runner scenario, Performance Centre load test, Tuning module session, Business process monitor profile

42. VuGen • What We can Do? • Set up recording options • Record the scripts • Add Comments • Insert Start and End Transactions • Perform Correlation • Add Checks • Add C programming Statements wherever required. • Insert Load Runner Functions if required. • Do Parameterization. • Add Rendezvous Point • Create Multiple actions If required. • Perform Run Time Settings

43. Welcome Screen - VuGen Single Protocol Script Multiple Protocol Script Creates a multiple protocol Vuser script. VuGen displays all of the available protocols and allows you to specify which protocols to record Creates a single protocol Vuser script. This is the default option

44. Script Section Used when recording... Is executed when... vuser_init a login to a server the Vuser is initialized (loaded)‏ Actions client activity the Vuser is in "Running" status vuser_end a logoff procedure the Vuser finishes or is stopped Vuser Script Sections • Each Vuser script contains at least three sections: • vuser_init • one or more Actions and • vuser_end. Load Runner

45. VuGen Editor

46. Recording Your Application • Click the Start Recording Button • For most Client / Server protocols, the following Screen opens • Recording Tool Bar (Floating Tool Bar)‏

47. Ending and Saving a Recording Session To complete the recording: • After you record a typical business process, you complete the recording session by performing the closing steps of your business process and saving the Vuser script. • Switch to the vuser_end section in the floating toolbar, and perform the log off or cleanup procedure. • Click the stop Recording button on the recording Tool Bar

48. Enhancing Vuser Script • After you record the Vuser Script you can enhance its capabilities by adding functions like • General Vuser Functions • General Vuser functions greatly enhance the functionality of any Vuser Script. All general Vuser functions have an LRPrefix • Protocol - specific Vuser Functions • Library functions used to enhance the script. (LRS- Windows, LRT- Tuxedo)‏ • Standard ANSI C functions • Enhancing the Vuser script by adding general C functions. • Like Adding Comments, Control flow statements, and so forth to your Vuser Script Cont…

49. Enhancing Vuser Script • Inserting Transactions into Vuser Script • Inserting Rendezvous point • Inserting Comments • Obtaining Vuser Information • Sending Messages to output • Log Messages • Lr_log_message • Debug Messages • Lr_set_debug_message • Lr_debug_message • Error and Output Messages • Lr_error_message • Lr_output_message Cont…

50. Enhancing Vuser Script • Handling errors on Vuser Script during execution(Runtime settings > Miscellaneous > Error handling)‏ • By default when a Vuser detects an error, the Vuser stops the execution • You can use the lr_continue_on_errorfunction to override the continue on errorruntime setting • To mark the segment, enclose it with lr_continue_on_error(1); and lr_continue_on_error(0); statements • Synchronizing Vuser Script • Synchronize the execution of Vuser script with the output from your application • Synchronize applies only to RTE Vuser Scripts Cont…