Tip: For a broader overview of Performance Test options and information on advanced options available in the UI, see Creating a Performance Test.
Apache JMeter is an open source load testing tool that enables you to execute performance tests on your app or website. To run a load test, create a script that will detail the steps of your testing scenario and then run it. You can run your JMeter script locally on JMeter, in the Cloud, or from behind a firewall on BlazeMeter. This article will take you through an overview of running a JMeter test on BlazeMeter.
- Write and Test Your Script in JMeter
- Upload Your JMX and Test Assets
- Calibrate Your Test
- Run Your Test
- Additional Test Options
Step 1: Write and Test Your Script in JMeter
You can create your script manually in JMeter or automatically by recording your scenario in:
For additional guidance on how to create and test your script in JMeter, see Step 1 and Step 2 in the Calibrating a BlazeMeter test guide.
Step 2: Upload Your JMX and Tests Assets
Follow these steps:
- In the main menu, click the Performance tab.
- Click Create Test.
- Click Performance Test.
- Click + to upload your JMX script and any additional test files, or drag the files over the Upload Script box.
- All the files in your account are downloaded to the remote servers at the beginning of each test.
- Files from the original test configuration may be updated or deleted at any time. Doing so will not impact a test while it's running.
Step 3: Calibrate Your Test
Before running your test at load, you must calibrate your test according to the Calibrating a JMeter Test guide. Configure your test options and set up overrides in preparation for running your JMeter Performance Test at full load.
CAUTION! Do not to skip this required step. If you do not calibrate, you may very likely see your test fail, hang, or terminate early due to overload of the engine available CPU or memory.
Step 4: Run Your Test
Click Run Test. You can also click Debug Test to validate your test configuration. For more information about debugging, see Debug Test: Low-Scale Test Run and Enhanced Logging.