Load Testing Process


With the ongoing technology advancements and digitization, everyone is trying to go online. The web traffic is increasing day by day. And this directly impacts on an application’s performance. Load testing of an application has become a necessity now. An application must be at least accessible or one may say stable up to 5,000 users. 
 
Conducting a load test manually requires a lot of human and machine efforts, which increases cost. To overcome this cost. A lot of automated performance software’s are made, which I have already discussed in my previous post. 

Before working on any of the automated software, one should first understand the load testing process. Here in this post I will be sharing the process of load testing using HP LoadRunner. You may find similar words like Plan, Create, Define, Run and Analyze as presented in the functional testing process (QTP). So the theme remains same and the parameter(s) varies with the type of testing you are about to perform.

Load Testing Process
Plan Load Test: 
This phase includes planning and configuration of user’s requirements. You should first see if the requirements are clear i.e. Is the application available for testing? Is the necessary hardware is available for a load test? How many virtual users are required to run?  What is the required response time? What is system threshold value or the capacity to bear the load?

Create Vuser script: 
This phase includes recording end user business actions or commonly known as a scenario, which is the automated generated script. When you are done with your script, analyze it. Check for dynamic values like a username, a password, a phone number or any other values. If such values exists, then you have to parameterize your test data so that concurrent users does not uses the same data.

Define scenario:  
This phase includes creating the load scenario in the Controller. For example connecting the load generator, initialization and stopping of the virtual users, defining run mode (real world schedule / Basic schedule), setting up the duration, and all other things which needs to be done to establish a load environment.

Run Scenario: 
This phase allows multiple activities like Drive, manage and monitor. The scenario in the controller is executed with the applied load. You can initialize, add, stop or even reset the running vusers, or you can also view the current action they are performing. Real time graphs generation lets you monitor application progress.

Analyze Results: 
This phase includes creation and reviewing the load results graphs, reports and performance. This is the most important part of performance testing, if you are unable to understand the result set, then all your efforts are in vain. To have a good comparision always start your load test with a single user and then increase to 10, 50, 100 or as per your requirements and analyze transaction time for all these executions.

So this is the load testing process, I hope it helps!! :) Share with me your valuable feedback and suggestion and help me improve the quality :)

Comments

Post a Comment

Popular posts from this blog

All about Dates using QTP

Majority of applications have Calendars controls. Automating a calendar can be painful at times if the textbox is disabled, and it only works if you select the date from the calendar widget provided on your website/application. I have been working on date controls for couple of months so thought about sharing all the findings with you people. So here i am summarizing some of the checks which can be handy working on date/Calendar controls. '''''' '''''' Compare start and End date For comparing end date validation, set today's date using Date function in start date textbox and set previous date in end date, and check if the validation is fired.   '''''startdate - set as todays date using 'date' Browser("").Page("").WebEdit("").Set Date '''''End date, set prev 5 days date Browser("").Page("").WebEdit("").Set DateAdd(...
Read more

LoadRunner Controller

Image
This is my second post from the HP LoadRunner series. As I discussed earlier, here I will be discussing an overview of LoadRunner Controller . So before going into detail, let me recap the prerequisites. Create script – Checked Replay Script – Checked Updating script if required (Add transaction, Parameterization and Content Check) – Checked  Runtime settings and Iterations – Checked Assuming the script is absolutely fine i.e. error free and ready to be passed on Controller, let us get familiar with the UI first. I will be using LoadRunner 9.5, the screens may vary at your end depending on the version you are using.   The UI The Controller has a Title bar, Menu bar, tool bar and a Status bar. After these we have multiple sections or panes.   The first is Scenario Groups pane. We can add multiple scripts or a single script and name them as a Group.  Next is Scenario schedule, here we define how the load will be passed and executed. We have two types o...
Read more

Working with WebRadioGroup

QTP WebRadioGroup means a radio button on the web page. Identifying and working with them can be easy or difficult. Sometimes they works out fine and at times executing the same code gives you error. If you have two radio buttons on the screen for example Gender selection options the code below might give problem. Browser("").Page("").WebRadioGroup("").Select "M" Where "M" can be the id or the value of the radio button (Spy the object). So what is the problem in the code above? As there are two radio buttons QTP identifies them as same, so we need to differentiate between them. Index is a property by which you can differentiate, it tells the position of the object. So if we write the same code below with an additional index property it will work fine. Browser("").Page("").WebRadioGroup("html id:=" ,"index:= 1").Select "M". This code is intended to select a radio button among two, what ...
Read more