Taurus Tool for Continuous Testing

1.16.49 · active · verified Tue Apr 14

Taurus (bzt) is a free and open-source automation-friendly framework for Continuous Testing. It simplifies the complexity of performance and functional test execution by acting as a wrapper for popular testing tools like JMeter, Gatling, Locust.io, and Selenium WebDriver. The current version is 1.16.49, released on February 23, 2026, and it maintains a regular release cadence with updates and new features.

Warnings

gotcha Taurus orchestrates various external testing tools (e.g., JMeter, Gatling, Selenium, Locust.io). While Taurus can auto-install some of these, you often need to ensure their prerequisites (like Java for JMeter) are installed and configured in your environment for optimal and stable operation.
Fix: Consult the Taurus documentation for specific executor requirements. For JMeter, ensure Java is installed and accessible. For specific versions of underlying tools, configure their paths in your Taurus YAML file (e.g., `modules.jmeter.path`).
gotcha When combining multiple configuration files or using command-line overrides, Taurus merges these configurations. Later specified files and command-line options will override earlier values, which can lead to unexpected behavior if not understood. Configuration includes special prefixes (`~` to overwrite, `^` to delete).
Fix: Familiarize yourself with Taurus's configuration merging rules. For debugging, check the `merged.yml` or `effective.yml` files in the artifacts directory to see the final applied configuration. Prioritize using `~/.bzt-rc` for user-specific settings and command-line flags (`-o`) for temporary overrides.
gotcha It is highly recommended to avoid placing sensitive information such as API keys or authentication tokens directly within your main test configuration YAML/JSON files. These files may be shared or included in artifact directories.
Fix: Store sensitive data in your personal per-user configuration file (`~/.bzt-rc`) which is not copied to artifact directories, or use environment variables, and reference them in your test configurations.
deprecated The `nose executor` was officially removed in Taurus version 1.14.1 (released February 2020).
Fix: If migrating from older Taurus configurations, update your test setup to use supported executors like Apiritif, PyTest, Selenium, or other integrated tools.

Install

pip install bzt Install latest version
pip install --upgrade wheel setuptools Cython pip install bzt Recommended installation

Imports

bzt
```
bzt <config.yml>
```
Taurus is primarily a command-line interface (CLI) tool that consumes YAML or JSON configuration files. Direct programmatic import and execution of the `bzt` module is not the standard or recommended user interaction pattern.

Quickstart

Create a YAML configuration file (e.g., `test.yml`) defining your test scenarios and execution parameters, then run it from the command line using `bzt <filename>`. Taurus will execute the test and provide a summary of results.

import os

config_content = """
execution:
- concurrency: 10
  ramp-up: 1m
  hold-for: 1m30s
  scenario: simple
scenarios:
  simple:
    think-time: 0.75s
    requests:
    - http://blazedemo.com/
    - http://blazedemo.com/vacation.html
"""

with open("test.yml", "w") as f:
    f.write(config_content)

print("Created test.yml. Run with: bzt test.yml")
# To run programmatically (not recommended for general use, primarily for internal/advanced):
# from bzt.cli import main
# main(['test.yml'])

view raw JSON →