HP LoadRunner - What it is and How it works
Download as PPTX, PDF1 like954 views
HP LoadRunner is a load testing tool from Hewlett Packard Enterprise used to test applications by simulating thousands of users concurrently. It records user interactions with an application and replays them while measuring system performance under different load levels. Key components include Load Generators that simulate users, a Controller to manage test runs, and an Analysis module to report on results. LoadRunner scripts are typically created using ANSI C, but also support Java, .NET, and JavaScript.
HP LoadRunner - What it is and How it works
- 1. HP LoadRunner Developer(s) Hewlett PackardEnterprise Stable Release 12.53 OS Microsoft Windows &Linux Type Load testing tool(s) License Proprietary Prepared by DhrumilPatel
- 2. 1. Introduction I. HPE LoadRunner is a software testing tool from Hewlett Packard Enterprise. In Sept 2016, HPE announced it is selling its software business, including Mercury products, to Micro Focus. II. It is used to test applications, measuring system behaviour and performance under load. HPE acquired LoadRunner aspart of its acquisition of Mercury Interactive in November 2006. III. HPE LoadRunner can simulate thousands of users concurrently using application software, recording and later analysing the performance of key components of the application. January 31, 2017 © Dhrumil Patel 2
- 3. 2. Architecture The key components of HPE LoadRunner are: I. Load Generator generates the load against the application by following scripts II. VuGen (Virtual User Generator) for generating and editing scripts III. Controller controls, launches and sequences instances of Load Generator - specifying which script to use, for how long. I. During runs the Controller receives real-time monitoring data and displays status. IV. Agent process manages connection between Controller and Load Generator instances. V. Analysis assembles logs from various load generators and formats reports for visualization of run result data and monitoring data January 31, 2017 © Dhrumil Patel 3
- 4. 3. How LoadRunner Works I. LoadRunner simulates user activity by generating messages between application components or by simulating interactions with the user interface such as keypresses or mouse movements II. The messages/interactions to be generated are stored in scripts. LoadRunner can generate the scripts by recording them, such as logging HTTP requests between a client web browser and an application's web server. January 31, 2017 © Dhrumil Patel 4
- 5. Figure: How LoadRunner Works 1 January 31, 2017 © Dhrumil Patel 5
- 6. 4. Support Modules are available to enable HPE LoadRunner to capture, replay and script different application and networking technologies. These include support for: I. Applications using microsoft .NET and java II. Database servers such as microsoft SQL server and oracle III. Internetworking protocols such as DNS, FTP and LDAP IV. E-mail protocols including IMAP, MAPI, POP3 & SMTP V. Remote client technologies such as citrix ICA and RDP. HPE LoadRunner client emulation scripts are usually created using the ANSI C programming language. However, Java and .Net programs can also be run by HPE LoadRunner. Version 12.50 added the use of JavaScript for Web- HTTP/HTML scripts. January 31, 2017 © Dhrumil Patel 6
- 7. Final Release Version Service Pack Release Date Notes 12.53 Patch 4 January 4, 2017 LoadRunner 12.53 Patch 4 contains various enhancements, and provides support for the following: I. HPE Mobile Center 2.20. For details, see the Mobile Center Help. II. HPE Network Virtualization (NV) 12.53 Patch 1 III. Google Web Toolkit (GWT) support: GWT Request Factory GWT 2.7.0 Verified for use with GWT 2.8.0 January 31, 2017 © Dhrumil Patel 7
- 8. LoadRunner Screenshots January 31, 2017 © Dhrumil Patel 8
- 9. January 31, 2017 © Dhrumil Patel 9 Transaction Response Time Quickly see response time over elapsed time 1
- 10. January 31, 2017 © Dhrumil Patel 10 2 Easily Create user transaction Automatically create new scripts.
- 11. January 31, 2017 © Dhrumil Patel 11 3 Average Transaction Response Time View different measures of response time.