HP LoadRunner is a tool from HP which is used for performance testing of an application. The tool is designed to generate a specific load on the application. During this phase, it can be determined how the application behaves under different load conditions. This LoadRunner tutorial is suitable for manual tester who have no experience in performance testing. HP LoadRunner Tutorial Topics. Basics of Performance Testing and Introduction to LoadRunner Before we start using LoadRunner, it is important to have a basic understanding of Performance Testing and why we need to test the performance of any application.

It is also helpful to have a brief idea of the various modules in LoadRunner. In this article, you will learn. What is Performance Testing? Performance Testing is conducted to see how the application behaves under various load conditions.

Performance testing can be broken down into the following categories. Load Testing – This category looks at whether your application meets the Service Level Agreements which have been defined when the system is subject to a particular load. For example, suppose you have a login page for an application. There could be a defined SLA defined saying that this page should always load in 2 seconds.

Hence no matter how many users hit the application at one time, this page should always load within that defined time frame. Load testing can also be used to determine the breaking point of your application. So it could determine that for a user load of 100 users, the application just fails to load.

AnalysisLoadrunner

Stress Testing – This is normally conducted to find issues that would prop up whenever there is a high load on the system. For example there can be cases wherein the memory heap size may not be enough when an application is subject to a high load. In such cases certain steps may need to be taken to ensure the application can work under loads. Capacity Testing – This is used to determine what the future growth requirement for an application is if the load on the application does increase in the future. So questions like “Does the Infrastructure require more memory or CPU to sustain a high load” can be answered during this testing phase.

Performance Testing is normally conducted after System/Integration Testing, in the entire testing life cycle. The entire testing life cycle is depicted in the below diagram. Once the System has been validated for its functionality during the System and Integration testing phase, performance testing is conducted. This is done before the UAT or User Acceptance Testing phase. Why do we need Performance Testing? Let’s consider a popular site which I am sure everybody is aware about – Facebook.

Let’s look at some of the user statistics for Facebook. There are currently over 1.71 billion active users on Facebook on a monthly basis. There are currently over 1.13 billion active users who log on to Facebook on a daily basis. There are 1.57 billion mobile active users on Facebook. There are around 10 million websites which have the Like and Share Buttons for Facebook The above numbers are just staggering. Even with the above numbers, The Company needs to ensure that normal functionality on Facebook should perform as it should. Would anyone want to wait for 1 hour to log onto Facebook because of the load on the application.

Analysis

Loadrunner Analysis Report Template

The answer is obviously ‘No’. So the only way to ensure that the web site behaves as it should under a heavy load is to ensure that proper performance testing is carried out to replicate the high number of users on the application. Let’s look at another popular eCommerce site of Amazon.

Amazon has nearly 181 million visitors per month on the site. Just Imagine if ever the Amazon site were to go down if the load on the system was not accounted for.

Forbes has predicted that Amazon would lose around 66,240 USD per minute if ever the site were to down. This is a staggering loss to the company.

One can just understand how important it is to conduct a performance test for an application to see how it would behave under various load conditions. What is LoadRunner? The LoadRunner is a performance testing tool which was initially designed by the company Mercury Interactive. It was later absorbed by Hewlett Packard when the latter acquired Mercury Interactive in November 2006.

The most recent version of LoadRunner is 12.53 Patch 1 as per June 2016. LoadRunner is used to simulate the actual user activity on an application. This user activity is multiplied with the help of running virtual users in parallel. In order to test your application, you need to ensure you have the right protocol purchased along with the LoadRunner tool. So for example, if you wanted to test a web application, you would need to have the Web(HTTP) protocol license. LoadRunner is designed to work with a wide number of protocols. The entire list of protocols is given below. Trane xe1000 specs.