Differences

This shows you the differences between two versions of the page.

--- tutorial:load_testing [2020/12/31 19:30]
admin [Model Execution with VUs]
+++ tutorial:load_testing [2021/01/05 03:00]
@@ Line 1: / Line 1: @@
-====== Tutorial: Load Testing with Runtime Servers ======
-Learning Objectives:
-  * Virtual Users (VUs)
-  * Model execution with VUs
-  * Multi-model execution
-  * Load testing with multi-browser
-  * Load testing with Runtime Servers
-  * Load testing with cloud-based services
-  * Simulating production load
-  * Performance testing
-===== Virtual Users (VUs) =====
-Virtual Users (VUs) is an important concept in load testing and stress testing with each VU representing one testing session.
-In //TestOptimal//, VUs are implemented with separate processes (threads) to execute the test cases generated from the model.
-A model is executed with one or many VUs.  In the web application / website load testing, VU is used to simulate concurrent users.
-Unlike typical load testing tool which submits pre-designed http packets or scenarios, //TestOptimal// can re-purpose models to dynamically generate test cases with the help of sequencers to simulate the more realistic production load on the system.
-===== Model Execution with VUs =====
-When you execute a model, it uses one VU by default.  You can change the number of VUs to be used for model execution in the //Execution Settings//:
-{{wiki:idescreen:ide_execsettings.png?300}}
-Set the field "Threads (VUs)" to the number of virtual users you wish to simulate running your AUT.
-You can also change how fast you want to ramp up the VUs by setting the "Thread Delay (ms)" before starting next VU.
-For load / stress testing, typically you will want the model and all of its VUs to be running for a desired period of time.  You can do so by setting "Elapse Time (mins)" in "Model Execution Stop Conditions" section before running the model.