Loadster Load Testing by RapidValue Solutions

Loadster Testing

By: Suja B & Krishnalal E B

.Net Developers, RapidValue

Loadster Testing

© RapidValue Solutions

Contents

Executive Summary ...................................................................................................................................... 3

Project Repository ............................................................................................................................................................................ 3

Dashboard ......................................................................................................................................................................................... 3

Steps to perform load testing ........................................................................................................................ 4

Conclusion .................................................................................................................................................. 23

Loadster Testing


Executive Summary

This document explains about Loadster Load testing and provides the details about the steps that

are required to perform the load test. This document is prepared after the successful

implementation of the Load Test in one of our customer projects. The blog, essentially, gives you

an idea of how Load Testing is considered to be a method to determine how an application will

behave under load. “Load”, generally, refers to the total user traffic at a given time. This

document also explains how Load testing software can be used to gain knowledge about several

different metrics like stress, stability, spike, scalability, baseline.

Loadster workbench is an integrated environment which enables you to perform load testing.

Load test can be performed using any number of virtual users. It gives us provision to record and

edit the scripts and the test results are obtained after performing the test. It has an in-built load

engine through which we can perform load testing with concurrent virtual users.

Project Repository

Loadster has a repository called project repository for each project, script etc. Test results, after

completing the load test, is also stored in this repository.

Dashboard

When the load test starts providing information, regarding the number of users, time taken to

complete the test is displayed on the dashboard. In spite of that, there are number of options

provided on the left side of dashboard namely response times, network throughput, transaction

throughput, transaction, error, virtual user, and load engine information. You can view a graph of

load test by clicking on any of these options as the load test runs.

https://www.loadsterperformance.com/

Loadster Testing


Steps to perform load testing The steps included in load testing are as follows:

Step 1: Scripting

It represents the actions performed by a user or a number of users during load test. It can be

created manually or scripts can be recorded. Multiple number of scripts can run during a load

test.

a) Recording Scripts

Configure the port: Loadster has an HTTP/S proxy that can record traffic between your

web browser and the applications you are testing. The proxy runs on localhost port 1997

by default.

Configure the web browser to use this port as proxy for recording traffic. For eg: In

Mozilla, Select options >Advanced >Network >Settings, select Manual proxy

configuration to configure the port. Click ok.

Click on the record button in the script editor for recording the script.

Loadster Testing


All the actions performed by the user in the above web browser will be recorded. After

completing the recording, click on „Stop Recording‟.

Filter the unwanted requests by unchecking the respective recorded scripts. Click on done

recording.

Then, the recorded traffic will be appended to the script.

b) Playing Scripts

After recording the script, run the script with a single virtual user.

Successful commands are indicated by three green dots under the http command.

Errors are indicated by three red dots under the http command.

Step 2: Scenario

It is used to create a number of virtual users during a load test. We can configure the number of

users, scripts to be run for the users and load engine.

Loadster Testing


a) Creating a scenario

After creating the project a scenario will be created. To add the virtual users click on „+‟

button.

There are options to edit the number of users included in each group.

A graph on the top shows the details of virtual user group. Each user group is

indicated by different color.

There is a provision to add or remove user groups by clicking the „-„button.

You can, also, change the built-in-load engine and select other option from the

list.

Loadster Testing


b) Running Load Test

Once scenario has been created, click on launch test button, to start load testing.

A popup displaying the fuel details is displayed. Click on „ok‟ button.

A test dashboard window will be displayed which contains Response Times, Network

Throughput, Transactions, Transaction Throughput, Errors, Virtual users and Load

engines as shown below:

o Response Times: It is the time taken by a page or HTTP request to respond. On

clicking on the response times in the left side bar, a graph will be displayed which

indicates the response times per page for the duration of the test.

Loadster Testing


o Network Throughput: It indicates the amount of data transferred between loadster

and the application during the load test. It is expressed in Megabits per Second

(Mbps). There is also a cumulative throughput graph which indicates the total amount

of uploaded or downloaded data during the load test. It is expressed in Mega Bytes

(MB).

Loadster Testing


o Transactions: This section displays a graph which shows any transaction (pages,

hits, and errors) as the load test runs.

Loadster Testing


o Transaction Throughput: It displays a graph which indicates the number of actions

completed within a specified unit of time.

Loadster Testing


o Errors: It displays any error which has been encountered during load test. There are

3 types of error graphs:

Errors by type: This graph indicates how many times a particular error has

occurred. Each error is indicated by a different color and the count is also

shown in the graph.

Loadster Testing


Errors by page:-This graph indicates the number of times an error has occurred per

page. It shows the page details and the number of errors in each page.

Loadster Testing


Error breakdown: It displays the Group, User, Location, Error Type and Count

Information for each error occurred.

Loadster Testing


Virtual Users: This graph shows the virtual user progression and total number of

users in the test.

Loadster Testing


o Load Engines: This shows information about CPU Utilization, Thread Count,

Memory Utilization and Latency.

CPU Utilization: This graph shows information about how busy is the load

engine‟s CPU. If more than one load engine is used, each one will be

indicated by a different color.

Loadster Testing


Thread Count:-It indicates the total number of threads in use by a load engine.

Loadster Testing


Memory Utilization: It shows the amount of memory used by a load engine.

Loadster Testing


Latency: This graph displays the delay between loadster workbench and load engine.

It is expressed in seconds. There should be an appreciable network connection in

order to decrease the latency.

Loadster Testing


A popup appears when the load test is finished. Click on „ok‟ button.

A test result, corresponding to the load test that is executed, is generated.

Loadster Testing


Step 3: Analyzing the test results

a) A test report will be saved in the repository when the load test is completed. You can

either rename the display name of the report or delete the report.

b) Customizing the report: On clicking the „customize‟ button in the report you can enter the

title, summary and notes on the report.

Loadster Testing


The resulting test report after customization is shown below:

Loadster Testing


c) Exporting an HTML report:- You can export the test report generated in HTML format

by clicking on „Export as Html‟ button. Then, you should specify the location where the

document should be exported. Once it is saved, a popup will be displayed. Click on „Ok‟

button.

Loadster Testing


Conclusion Loadster is a load testing tool for websites, web applications and HTTP web services. It helps you to,

easily, simulate a realistic and a large volume of users to find bottlenecks, improve reliability, and

optimize user experience. Loadster Performance is the creator of Loadster that is a commercial load

testing tool. It helps to simulate and predict how web applications will behave under heavy load. This

tool is best to identify performance bottlenecks in your application. Load test your applications now!

Loadster Testing


About Us

RapidValue is a leading provider of end-to-end mobility and cloud solutions to enterprises

worldwide. Armed with a large team of experts in consulting, UX design and application

engineering, along with experience delivering global projects, we offer a range of services across

various industry verticals. RapidValue delivers its services to the world‟s top brands and Fortune

1000 companies, and has offices in the United States and India.

Disclaimer:

This document contains information that is confidential and proprietary to RapidValue Solutions Inc. No part of it

may be used, circulated, quoted, or reproduced for distribution outside RapidValue. If you are not the intended

recipient of this report, you are hereby notified that the use, circulation, quoting, or reproducing of this report is

strictly prohibited and may be unlawful.

www.rapidvaluesolutions.com/blog

www.rapidvaluesolutions.com

+1 877.690.4844

[email protected]

Date post:	16-Feb-2017
Category:	Technology
Upload:	rapidvalue
View:	307 times
Download:	0 times

Loadster Load Testing by RapidValue Solutions

Technology