Taurus is an open source test automation tool that extends and abstracts leading open source tools including JMeter, Gatling, Locust.io, The Grinder, JUnit, Selenium, and more. Taurus provides a simple way to create, run, and analyze performance tests.
Taurus can consume configuration files written in JSON or YAML languages, which are very human-readable. For instance, 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 will look as simple as:
As you can see, it’s only eleven lines of simple human-readable language that represents a (more or less) complete load scenario. It’s really simple to use.
This is the whole idea of Taurus: to provide a unified, simplified way of configuring and running automated tests, then present the results in the most effective form. To learn more about Taurus, first check out Taurus's Beginner's Course, then for more information about Taurus's configuration syntax, visit the Taurus Tool Documentation.
- Creating a New Taurus Test
- Upload a YAML/JSON Script with Test Assets
- Failure Criteria
- APM Integration Options
- JMeter Properties
- DNS Override
- Network Emulation
- Ready to Run!
You can start creating your Taurus test in the BlazeMeter GUI by clicking on the "Create Test" button on the top navigation bar. On the next screen, click the "Taurus" button.
At the top of the screen, you'll find a central location to upload your YAML/JSON script. Here, you can either click the "+" button to browse to your script or drag the script from your desktop to the "+" button.
- 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.
Before moving forward with the test, make sure the uploaded script shows "Passed" under "Validation status" -- if it doesn't, there may be a syntax or other problem with the script.
If you require more information regarding uploading files to the test configuration page, please refer to this article.
Under the 'Configuration Preview', you will see the YAML/JSON code of the file you uploaded.
If you're running a JMeter test with Taurus and have uploaded a CSV file with your script, then the option to "split CSV files" appears below the script preview. You may check this box to enable the feature, which you can learn more about here.
All done? Now just give it a name and you're Taurus test is ready to go!
Note: An alternative method is to call Taurus from the command line, then have the test run in BlazeMeter automatically by adding "provisioning: cloud" to the configuration. This method doesn't even require a web browser! To learn more about this alternative method, check out the Taurus documentation on the topic here.
This option is disabled by default but may be enabled if you wish to add KPI thresholds for which your test may pass or fail. Learn more about how these optional thresholds can be configured in our article here.
- New Relic APM: Just enter your New Relic API key here and you'll be able to select profiles. Further details here
- New Relic Infrastructure: Enter your New Relic Insights API Query Key, then provide your profile name and account ID to include time series data from New Relic Infrastructure. Further details here
- CA Technologies APM: Integrate your CA APM application to run and investigate load tests through test metadata. Further details here
- Cloudwatch: Integrate your AWS application monitoring tool and you'll be able to select profiles and view your application server's KPIs. Further details here
- AppDynamics APM: Enter your account's details to access AppDynamics. Further details here
- DynaTrace APM: Choose a DynaTrace integration mode and the monitoring KPIs will be immediately available to you in your DynaTrace app. Further details here
These settings only apply if you have configured the Taurus test to run JMeter. This option is disabled by default but may be enabled if you wish to add JMeter properties to your test. You may also specify what version of JMeter to use, or allow the test to auto-detect the version for you. Learn more about how these properties can be added in our article here.
This option is disabled by default but may be enabled if you wish to specify alternative IP addresses for your hostnames. You can learn more about this option in our article here.
This option is disabled by default but may be enabled if you wish to forcibly impair the connection between BlazeMeter's test engine and your application server for testing purposes. You can learn more about this option in our article here.
You can now either run the test or run a debug of the test (to learn more about the debug option, please refer to this article).
Once again, make sure you name your test, save it, and then you're ready to go! Great! You've now successfully set up your Taurus test. Ready to move on to the next step? Read our article on Running BlazeMeter Tests to find out how.
Want to learn more about running a Taurus tests with open source tools? View our on-demand webcast How to Stop Waiting & Start Testing With Open Source Tools.