The amount of load is often the expected number of users, but you may also wish to soak test your application at multiple load levels.
Users Over Time for a soak test is a flat line: The duration of the test may be hours, days, or even weeks.
Two related load test types are baseline tests and high load tests. Once the test is completed, you can identify the time in the results that the application performance degrades or fails then, you can identify performance counters on the application or database server that explain why. If you target a production server, consider planning the test for off-peak hours. Keep in mind that this type of test will eventually disable the target application, so plan accordingly. Adding VUs slowly over time increases the precision of your results: you can determine how many VUs were hitting the application when it slowed or failed. If your Test Studio Load Test has enough VUs, the application under test will eventually begin to slow down and fail. Users Over Time for a stress test is a diagonal line from low to high: In Test Studio, create a stress test by increasing the number of Virtual Users (VUs) in your Load Test throughout the test. What are the performance bottlenecks that limit the load my application can support? How many users can my application support without slowing down? How many users can my application support without failing? Stress TestingĪ typical stress test begins with a small amount of load and slowly increase this amount throughout the test. Here are four common types of load test, and how to start building them in Test Studio. There are many types of load tests, each designed to answer specific questions. Download free 30-day trial Types of Load Tests
0 kommentar(er)
