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.