You've set up your test and you're ready to go! From the test configuration view, you can run it by either clicking the "Run Test" button to run a full Performance Test or the "Debug Test" button to run a low-scale Debug Test with enhanced logging.
Alternatively, if you've run the test previously, you can also run it from a previous test report, simply by clicking the play button to the left of the test name.
You'll then be asked if you're ready to launch the servers. Review the configuration, then click the "Launch Servers" button to start the test.
You can optionally check the "Run test in the background box" if do not wish to see the startup status view, in which case you'll be immediately returned to your previous view while the test runs in the background.
If you enabled running in the background, you can check on the running test using the "Reports" drop-down menu, beside which will be a count of currently running tests.
Summary Boot Screen
If you didn't check the run in background option, you'll see the following screen show up, which is the boot status of the engine(s) of your test:
You will see a summary of 4 colored statuses that the engines can be in, indicating their current status. The following is the list of statuses the engines can be in and what they mean:
- Pending - This indicates the percentage of engines are pending allocation on our end
- Booting - This indicates the percentage of engines have been allocated and are booting up
- Downloading - This indicates the percentage of engines that have started downloading all the test assets
- Ready - This indicates the percentage of engines that are ready to start
If you want to get more detailed information on your engines and their statuses, you will want to click on the "Show Engines" button:
Detailed Boot Status Screen
When you click the "Show Engines" button, you will see the following screen come up, which contains a more detailed breakdown of the engines running:
This screen will provide a more detailed list of each and every engine that is spun up for the test run.
NOTE: The filters described (with the exception of Status) will only give you the options used in you test. For example, if you run a test in Google Cloud Virginia and a Private Location, you will be able to filter based one (or both) of those locations and you will be able to sort by Google Cloud provider and Private Location provider.
The following a detailed breakdown of everything that appears on this screen:
|This is a link to the test configuration for this test run. The test here will be the name of the test you used.|
|This is the amount of time that has occurred since the start of the test run.|
|This will return the screen to the summary view described above.|
|This button will force start the test without waiting for the rest of the engines to be in "Ready" status|
|This button will start the test. This will appear when all engines are in "Ready" status.|
|This button will terminate the test, stopping all engines immediately upon confirmation.|
|The boot status of all the engines for this test run. See the summary view above for a description of all statuses that can show up here.|
|This will allow you to set the refresh rate of the table.|
|This will allow you to filter the engines by scenario. The "Show only added scenarios" option will show you only the scenarios you added to a test using this feature.|
|This will allow you to filter the engines by location.|
|This will allow you to filter the engines by the cloud provider. This list will be AWS, Google Cloud, Azure, and Private Locations.|
|This will allow you to filter the engines by status. The "Show only not Ready" option will select all options but the Ready status, so you will only see engines that are not in "Ready" status.|
|This will allow you to filter the engines that use dedicated IPs or all engines.|
|The first icon will bring you to the system log for that specific machine. See the System Log section for more details.|
The following image of the detailed boot screen covers a number of data on each engine in your test:
|Scenario||The scenario this engine is running|
|Location||The cloud or private location where this engine is running|
|Cloud Provider||The name of the cloud provider where this engine is running|
|Script||The script this engine is starting with|
|IP||The IP address of this engine|
|Status||The status the engine is currently in|
|Session Id||The sessionId for this engine|
Note: If your test takes much longer to start, it may be indefinitely hung due to an incorrect configuration. There are a number of common causes for this problem which are covered in the Blazemeter Test will not Start knowledge base article.
If you wish to see the system log, you can click on little boxes at the bottom right-hand side of the screen.
There are four checkboxes at the top of the system log: System, User, Autoscroll, and New Messages Alert.
NOTE: You will only be able to view the system log for one session at a time.
- The System option, when checked, simply ensures system messages are included in the log.
- The User option, when checked, will show the user logs form the system log.
- The Autoscroll option, when checked, will ensure the window automatically scrolls as new lines fill it up.
- The New Messages Alert, when checked, will provide you with notifications for every new action.
You can complete other tasks while the test is running in the background, such as viewing reports or configuring and running other tests.
You can wait a few minutes until the test ends or you can stop the test yourself. If you need to manually stop the test for any reason, refer to our guide on Stopping a Test.
Want to learn more about running BlazeMeter tests? Watch our on-demand recording, How to Make JMeter Highly Scalable and More Collaborative With BlazeMeter