Trail: StressTest

Performance Testing : StressTest

KnowledgeBase :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register

Stress Test

Test application under a load for a period of time to discover the ability of the application to handle workload. Most commonly collects various performance related measurements based on tests that model varying loads and activities that are more "stressful" than the application is expected to encounter when delivered to real users.

Sub categories may include:

Stress testing involves subjecting the product to heavy loads or stresses. Unlike volume testing, a heavy stress test is a peak volume of data encountered over a short span of time. If a product can only handle 50 simultaneous users on the system, then exercise the product with 51, 100, 200, etc users.

Any testing involving challenging inputs or environments; where challenging means at, near, or exceeding the actual operating limits of the product under test (not merely its stated limits). Stress testing is done for the purpose of understanding how reliability and performance degrades over time as the product is "stressed" by such challenging circumstances. Good stress testing requires that the test designer analyze the potential vulnerability of the product to stress, so that the product is indeed challenged in every relevant manner and dimension.

Verifies the acceptability of the target-of-test's performance behavior when abnormal or extreme conditions are encountered, such as diminished resources or extremely high number of users.

Stressing and testing the system at and beyond its limits, e.g., at maximum throughput or at overload.

Stress Tests are tests that use real-world distributions and user communities, but under extreme conditions. It is common to execute stress tests that are 100% of expected peak expected user-load sustained over 8-12 hours, and 150% expected peak user-load with normal ramp up and ramp down time. These tests are generally only executed after several rounds of tuning. If all components of the system continue to function normally, within reasonable times (generally not more than 150% of stated performance goals), a Stress Test passes.

A stress test is a type of load test designed to determine how much load a Web application is able to handle. In the test, a considerable load is generated as quickly as possible in order to stress the application to its limit. To intensify the load on the application, the time between transactions is minimized and the modem simulation speed is set to the maximum possible. A stress test helps in ascertaining, for example, the maximum number of requests a Web application can handle, and when an application will break down because of the load[1].

1. From "Load Testing for eConfidence" by Segue.


There are no comments on this page. [Add comment]

Page History :: 2006-02-10 11:51:50 XML :: Owner: Roland Stens :: Search:
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by Wikka Wakka Wiki
Page was generated in 0.0185 seconds