CAUTION! Blazemeter now predominantly runs on the V4 ("Version 4") architecture, whereas the legacy V3 ("Version 3") architecture has been deprecated and is no longer supported. This and other legacy articles apply to V3 tests for customers who have not yet fully migrated to V4. For more details about the current V4 testing architecture, please begin with our guide, Benefits & Advantages of Blazemeter's New Infrastructure & UI.
The Multi Test is used for distributed load testing.
The Multi Test synchronizes and aggregates the results from several test sessions into a single aggregated report.
The Multi test configuration includes individual test configurations orchestrated to run simultaneously. Each test is still individual and can be run independently, Regardless of the Multi Test.
Starting A New Multi Test
To use the Multi Test setup, you need to follow these instructions:
Start creating your 'Multi Test' by clicking on the Performance tab, then the "Create Test" button on the top navigation bar and then select Multi Test.
Setup A Multi Test
1. After you have created a new Multi Test you will see a three options screen. You can add or create new JMeter Tests, 'URL/API' Tests, or 'Webdriver' Tests and add them to the new 'Multi Test' you are creating.
2. The 'DRAG & DROP TESTS HERE' option enables you to simply grab tests from the tests list on the left panel, and drop them in the Multi Test and by doing so adding them to the Multi Test.
If you do not see the test list on the left, click on 'Tests' on the top navigation bar, and then 'Show all tests'.
Configuring The Test
After adding all the different tests you wish to run simultaneously using the Multi Test, you might want to change their configuration. Please note that you can configure any of the tests in the Multi test to be entirely different from the other since there is no dependency between the standalone tests at all.
You can change the location each test will generate traffic from and the basic configuration of the test. If you wish to make any changes to further options, e.g 'command line arguments' or 'JMeter Properties' then you can click on 'Edit Original Test' and make the necessary changes.
Configuring a standalone test is easy as:
1. Click on that test in the Multi Test view.
2. Change the configuration as you please.
Running The Multi Test
2. Further more, you are given a choice to select 'Synchronized Start' which will make sure all servers are up before actually starting the test. This option is useful if you have a concern that some servers or locations are significantly slower than others and you wish to synchronize them.
3. After you pressed 'Launch Servers', you will be shown the 'Booting' Window which shows you the progression of launching the load engines and consoles across the entire Multi Test.
Force Starting a TestUnfortunately, sometimes a load engine might fail to initiate due to a defunct AWS instance.
When the test is in its' booting stages and the 'Servers Status' is shown, You might notice that for 10+ minutes, one of your tests is failing to load all of its pre-configured engines. In this case, instead of waiting forever for the test to start, and by that not starting the test at all, you can click on 'Force Start' and the test will start to run with all the engines that are already up and waiting. If the defunct engine will successfully start along the way, its' data will be aggregated along with the rest of them in the aggregated Multi report. That's it! Your Multi Test is up and running!