Creating a Taurus Test
Taurus is an open source test automation tool that extends and abstracts the functionality of leading open source testing tools, including executors such as JMeter, Gatling, Locust.io, JUnit, Selenium, K6, and more. Taurus provides a unified, simplified way to configure and run automated performance tests, then present the results in the most effective form. To learn more about Taurus, see: Beginner's Course and Taurus Tool Documentation.
Important: If you want to run Taurus tests on your local machine using the Command Line Interface (CLI) and view the reports on BlazeMeter, note that VUs (Virtual Users) used in tests will be counted towards your plan limit and reflected in usage reports and credit balances.
Taurus can consume configuration files written in JSON or YAML languages that are human-readable and simple to use.
A simple load test with 10 concurrent users, a ramp-up time of 1 minute, a duration of 2.5 minutes and hitting the site blazedemo.com with HTTP GET requests:
scenario: Thread Group
- label: blazedemo
- Create Taurus Performance Test in BlazeMeter
- Upload a YAML/JSON Script with Test Assets
- Run Taurus Tests in BlazeMeter
- Run Taurus Tests on Your Local Machine (CLI)
Create a Taurus Performance Test in BlazeMeter
Follow these steps:
- In the main menu, click the Performance tab.
- Click Create Test.
- Click Performance Test.
Important: Taurus supports Selenium scripts but we do not recommend running Selenium tests as performance tests, as explained in our KB article Can I use Selenium for Load Testing? We recommend using Selenium tests for functional testing. For more information, see Creating a GUI Functional Test.
Upload a YAML/JSON Script with Test Assets
Click + to upload your script and any additional test files, or drag the files over the Upload Script box.
included-configs setting is not supported in the BlazeMeter cloud. If your YAML references a secondary YAML via
included-configs for additional configuration settings, merge all settings into one YAML before uploading your test.
For more information, see:
Note: After uploading your YAML file, you may notice that Load Configuration and Load Distribution options disappear from the UI. When you are running a Taurus test, these settings must be configured directly via the YAML, not via the UI. For more information, see Load Profile. Taurus uses different terminology for some settings. The Hold-for setting in a Taurus YAML is the equivalent of the Duration setting in the Load Configuration section of BlazeMeter UI.
Under Configuration Preview, you will see the YAML/JSON code of the file that you uploaded.
If you are running a JMeter test with Taurus and have uploaded a CSV file with your script, the option to split CSV files shows below the script preview. Check this box to enable the feature. For more information, see Scenario Definition.
There are additional options to add to your test configuration. For more information, see:
You have set up your Taurus test.
Run Taurus Tests in BlazeMeter
Name your test.
(Optional) Click Debug Test to validate your test configuration.
For more information about debugging, see Debug Test: Low-Scale Test Run and Enhanced Logging.
Click Run Test.
Tip: If a long-running Taurus test is shown as aborted instead of terminating gracefully, make sure you have defined the
hold-for option in the Taurus YAML file. For example, when running locust tests that are provisioned to run in the cloud, you must configure a
hold-for in your test that is long enough to allow all configured iterations to complete.
Run Taurus Tests on Your Local Machine (CLI)
An alternative method is to call Taurus from the command line on your local machine, then have the test run in BlazeMeter automatically by adding provisioning: cloud to the configuration. This method does not require a web browser. For more information, see the Taurus documentation.
Important: If you want to run Taurus tests on your local machine using the Command Line Interface (CLI) and view the reports on BlazeMeter, note that VUs (Virtual Users) used in tests will be counted towards your plan limit and reflected in usage reports and credit balances. If your test exceeds the allocated VU entitlement or duration, the report will be stored, and you will receive a prompt to upgrade based on your current plan and desired configuration.