Stress Testing

Stress testing is seen as part of the process of performance testing which tries to identify the breaking point in a system under test by overwhelming its resources or by taking resources away from it. This helps to ensure that the system fails and recovers gracefully.
Stress Testing is done to uncover memory leaks, bandwidth limits, transactional problems, resource locking, hardware limitations and synchronization problems that occur when an application is loaded beyond the limits determined by the performance statistics.
Stress testing tools generate extremely high load on the Web server by simulating multiple client connections.

QEngine stress testing process is very simple and straightforward which is done in three easy steps:

* Record Your Stress Test Scripts
* Add dynamic data to the test and set load level
* Run stress test and analyze stress test results

Stress Testing Features

The key features that help you perform stress testing are:

Stress Test Recording

Stress test recording is made simple and easy with a point and click user action. You can record stress test scripts to capture any HTTP/HTTPS/SSL/AJAX requests.

Flexible User Scenarios and Dynamic Data Generation

To emulate the real-user activities, QEngine stress testing provides the flexibility to split the number of users accessing different parts of the web application performing different operations. You can also capture user diversity to simulate a variety of virtual users characteristics such as different connection speeds, different browser types, IP Spoofing and different servers/ports.

To capture real-life stress testing, you can generate dynamic data for the stress test. The values of session IDs or request parameters (Get/Post data) can be fetched from a number of ways (from dataset, hidden elements, previous response/url, cookies, etc).

Real-world Load Simulation

To stress test and identify the potential breaking points in your web application, QEngine supports the Burn-in mode and Mixed Load.

Burn-in Mode Load Test: The burn-in mode helps you to verify the acceptability of your web sites/web applications when abnormal or extreme load conditions are encountered for an extended period of time, such as diminished resources or extremely high number of users. You can exit the stress test only based on some specified exit criteria. Exit criteria allows you to set multiple criteria based on which the stress test should exit or the system should break, if one of the criterion is not met during the stress test execution. This goal based test methodology enables stress testers to set thresholds and parameters during stress test configuration to identify the breaking points. If not attainable, either the system should break or the stress test should exit.

next >>