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.
If you didn't check the run in background option, you'll next see a progress bar, telling you how much longer you need to wait. Launching servers in the cloud usually take 2-4 minutes. Tests involving a larger number of servers may take around 10-12 minutes.
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 our 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 three checkboxes at the top of the system log: System, Autoscroll, and New Messages Alert.
- The System option, when checked, simply ensures system messages are included in the 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