LoadRunner is one of the biggest name in the performance testing world. LoadRunner has a variety of protocol support which covers nearly all types of the software platform.
LoadRunner is developed by Mercury in 1999 and acquired by HPE in 2006 and named as HP LoadRunner. Later on, after the merger of Micro Focus with HPE gave it a new name called Micro Focus LoadRunner.
Functioning of LoadRunner
LoadRunner works on the concept of recording and replaying the user activities and generating the desired load on the server. It simply simulates the real world user’s actions and helps to identify the performance of the software application or system by generating virtual load.
The main steps include:
- Recording/Scripting : To capture the user action into a script. These scripts are run by generating virtual users.
- Test Execution : Replaying the script along with virtual load to simulate the real-world situation in the test environment.
- Result Analysis : To provide accurate result in terms of load handling capacity and responsiveness of the application. the Analysis tool generates the report (in pdf, HTML, excel etc. format) which concludes the test result.
LoadRunner Components
Micro Focus LoadRunner has the following components:
- Virtual User Generator or VuGen : It records end-user business processes and creates an automated test script in the form of programming language. The generated script is called as VuGen Script or Test Script.
- Load Generators : These are machines which generate the virtual load as per the requirement. During test execution, the Controller distributes each Vuser in the scenario to a load generator. Load generator is also used to simulates the geographical location of the users.
- Controller : It organizes, drives, manages, and monitors the load test. A controller is also used for workload modelling. Workload Modelling involves the creation of a test scenario as per NFR (Non-Functional Requirement).
- Agent : The LoadRunner agent sets-up a communication between the Controller and the Load Generator.
- Analysis : It helps to view, dissect and compare the results of the load tests. Analysis tool displays the result graphs and statistics to validate the test result against the defined NFRs (Non-functional requirement) and to find out the bottleneck (performance bugs). The analysis tool also generates a report based on the test result.
Performance Testing Roadmap
Performance Testing Roadmap can be broadly divided into 5 steps:
- Planning for Load Test
- Create VUGen Scripts
- Scenario Creation
- Scenario Execution
- Results Analysis (followed by system tweaking)
Why to choose LoadRunner?
There are many reasons to choose Microfocus LoadRunner as a Performance Testing tool:
- LoadRunner has a simple and interactive user interface.
- It removes the drawbacks of manual performance testing with its user-friendly components.
- LoadRunner limits the requirement of excess hardware. Since there are no physical users so a single Load Generator machine can generate multiple user load and reduces the requirement of hardware or physical machines.
- Easy correlation method (to handle the dynamic values coming from the server). Also, intelligent auto-correlation feature.
- Supports mobile and cloud performance testing.
- The flexibility of the controller helps to create the user load test of any pattern.
- Live graphs and statistics of client-side performance metric during the test.
- LoadRunner also supports to monitor the network and server resources to identify the bottleneck.
- A wide variety of graphs helps in result analysis.
- Option to generate the reports in multiple formats.
To learn more about LoadRunner you can also visit:
https://www.perfmatrix.com/micro-focus-loadrunner-tutorial/
Top comments (1)
Nice write-up.
Regarding the load tests tool, I suggest considering NBomber, a .NET tool for load testing. It's a modern and flexible .NET load-testing framework for Pull and Push scenarios, designed to test any system regardless of a protocol (HTTP/WebSockets/AMQP, etc) or a semantic model (Pull/Push).