Monday 3 June 2013

Microfocus Load Runner Introduction and Architecture

LoadRunner, now under Micro Focus since its acquisition of Hewlett-Packard Enterprise's software division, remains a top-tier performance and load testing solution. It enables thorough examination of system behavior and performance under various loads.

LoadRunner can simulate thousands of concurrent users, providing a realistic load environment for applications. It gathers data from critical infrastructure components like web servers and database servers for detailed analysis.

Consider a scenario like testing an Automated Teller Machine (ATM) application. While each client connects to a server, the total number of ATMs accessible to the public could be in the hundreds, experiencing peak loads during certain times, such as Monday mornings. Testing such scenarios practically with hundreds of physical ATMs is infeasible. However, with LoadRunner and an ATM simulator, one can simulate numerous users accessing the server simultaneously. Defined activities are repeatable, aiding in debugging and verifying fixes by reproducing specific user interactions.

LoadRunner supports various application protocols including Flex AMF, Citrix ICA, Remote Desktop Protocol (RDP), ERP/CRM (e.g., SAP, Oracle eBusiness, Siebel, and PeopleSoft), Databases, Mail Clients, Web Services, and AJAX TruClient.


File Extensions:
- VuGen: .USR
- Controller: .LRS (now .LRR)
- Analysis: .LRA


LOADRUNNER COMPONENTS 



The LoadRunner suite comprises three main components:

1. VuGen (Virtual User Generator): Used to create scripts for single-user scenarios and enhance them for multi-user testing.
2. Controller: Executes load tests and monitors servers during test execution. It creates scenarios and runs load tests, typically installed on a client machine with LoadRunner licenses for a defined number of users. Multiple controllers may be set up for different projects and performance engineers' use.
3. Analysis: Used to analyze test results, generate graphs, and create reports for stakeholders.





LoadRunner Environment:
The number of machines required depends on the test environment's scale. While all components can be installed on a single machine, larger tests may require distributed setups. 

For instance:
- Single Machine: Controller, VuGen, Analysis, and LoadRunner Agent Process
- Multiple Machines: Separate machines for controllers and load generators, distributed based on user licenses to handle larger loads efficiently.

Architecture of LoadRunner: