You can start creating your Performance Test in BlazeMeter's new and improved Test Creation Page.
Click on the "Create Test" button at the top of the navigation bar. Then, select 'New Beta Test' under the Test Creation Tools section. Do not forget to create the test within the relevant Project.
At the top section of the screen, under 'Scenario Definition', you'll find a central location to upload your test files (JMX script for a JMeter test, Scala script for a Gatling test, etc.). If your script utilizes a CSV data file and/or an external JAR file, please upload these files here as well.
BlazeMeter will automatically identify the format of each file you upload and classify it - a JMX file will be classified as Type 'JMeter', a CSV file will be classified as Type 'CSV', etc.
Select the main script that you would like to run in this test:
Once you check the main script from the files you uploaded, BlazeMeter will automatically recognize the Test type (JMeter for a JMX file, Gatling for a Scala file, etc.).
When running your performance test in BlazeMeter:
- During the test, the files in your account are synchronized every few minutes.
- You cannot delete files while the load test is running. Files can be deleted only when the test ended, or before it started.
- If you choose to upload a CSV file, make sure you remove the path from the CSV data set configuration controller, as the files will share the same folder. If you do this and you have more than one engine, you probably don't want two engines to execute the same login for the same user. To prevent that, you can check the 'Split CSV files with a unique subset per engine' option, and the users will be sent to different engines as follows: line one will go to engine one, line two to engine two, line three to engine one, etc.
If you require more information regarding uploading files to the test configuration page, please refer to this article "Uploading Files and Shared Folders".
For more information about using a CSV file in your test, please refer to this article "CSV file Upload".
You can control and override the load configuration of your test script, by using the drop-down buttons. Here is a quick explanation of each one:
- Total Users: Select the number of users you want. The number of Engines and the number of Threads per Engine are adjusted automatically according to this number.
- Rampup Time (sec): Select how fast you want the test to ramp-up.
- Rampup Steps: Select the number of steps for the ramp-up of your test. Note: this is automatically set to 0 (0 steps mean Linear Ramp-up).
- Duration (min): Set the full-time duration that you want the test to run for.
- On the right side of the 'Load Configuration' section, you will see a load preview graph.
You can distribute your test's Virtual Users load to multiple cloud locations by clicking the '+' button:
All you need to do is choose the cloud location (using the Locations drop-down buttons) and the % of Traffic for each location. Make sure that the % of Traffic for all the locations you choose adds up to 100%:
You can change the Max Users Per an Engine by clicking on the value next to it. BlazeMeter will automatically adjust the number of required Engines:
Additional options and integrations
- Failure Criteria: Set failure criteria for various metrics to fail the test if needed.
- APM integration:
- New Relic APM: Enter your New Relic API key here and you'll be able to select profiles. A profile is a preset that will be kept for your following tests, so you don't have to set all metrics every time you run a test.
- CA Technologies APM: Once you check this option, we will enable an HTTP headers integration with your CA Technologies APM.
- JMeter Version - Choose the JMeter version you would like to run the test on. While this is your choice to make, we strongly advise on choosing the latest JMeter release.
- JMeter Properties - You can set your JMeter properties here. This is a real-time feature whose properties will be sent to the engine while running the script. E.g., if you add hits with the value '100', or type in 'execute - true', these properties will be changed in the test while it runs.
- DNS Override: Use this if you want to inform the load test engine not to automatically go to the DNS, but rather to use a specific IP record instead. Just enter the appropriate IP and your script will be redirected without you having to change your labels.
On the left side of the screen, you can see a summary of the configuration you just set. You can also change the test's name, start the test, or duplicate or delete the test using the '...' button.
Great! You have now successfully set up your BlazeMeter test and you are ready to go! To run your test, read our next article "Running Your Test on BlazeMeter".