%% Last Updated: - [[2021-02-13]] %% %% date:: [[2022-09-22]] %% # [[Shakeout Test]] I often see customers testing out their new load testing script by running it with 10,000 users. Such an approach exposes them to unnecessary costs in the provisioning of the machines for a test that might fail, which it often does. Test out your scripts with a single user on your local machine. If that works, try it with two users. Then try it with ten users, with each one doing multiple iterations of the script. If that works, then you can consider doing a shakeout test on the cloud. A shakeout test is a low-load test that is intended to be a quick check to see that the script, the environment, and the entire set-up, are working as expected. Depending on the application, a starting shakeout test could consist of anywhere from 1 to 100 users for about 10 minutes. The goal of a shakeout test is not to expose performance bottlenecks; it is a chance to verify that: - the scripts are hitting the functionalities that were agreed upon with a low error rate - the environment is fully integrated and functional - the server monitoring is operational - the right people for the involved application teams are on board and watching the test It’s a rehearsal before the real tests begin. Depending on your comfort level and the responsiveness of the application, you can increase the number of users gradually until you’re ready to ramp it up. After shakeout tests are successfully executed (and no major errors are discovered), it’s time to move on to other test scenarios.