Install bzt with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• bzt
• jmx2yaml
• soapui2yaml
• swagger2yaml

Project history

The official README describes Taurus as a convenience wrapper that hides the complexity of performance and functional tests while relying on underlying tools such as JMeter, Gatling, Locust.io, and Selenium WebDriver. The project is free and open source under Apache 2.0.

The gettaurus.org documentation presents Taurus as a YAML-based command-line framework for load testing, continuous integration, reporting, and cloud-provider workflows. Its Git tag history starts at 1.0.0 and continues through a long 1.x series.

Adoption history

Taurus adoption is concentrated among performance-testing and CI users who already know tools like JMeter but want easier automation, configuration merging, and reporting. Homebrew packaging makes the `bzt` command easy to install on macOS developer machines.

Unlike broad Unix utilities, Taurus is specialized; the input facts list Homebrew as its package-manager channel here. Its wider distribution path is Python packaging via `pip install bzt`, which the upstream README recommends.

How it is used

Users create YAML or JSON test configurations and run them with `bzt config.yml`, or launch shorthand flows such as `bzt my-existing.jmx` for JMeter files. The command-line docs describe config merging from base config, `/etc/bzt.d`, `~/.bzt-rc`, user-supplied configs, generated JMX shorthand, includes, aliases, and overrides.

`~/.bzt-rc` is specifically documented as a per-user preference file and a recommended place for API keys and tokens because it is not copied into artifact directories.

Why package nerds care

Taurus is package-interesting because it turns a stack of heavyweight test tools into one CLI entry point. Installing `bzt` gives developers a small command surface over JMeter, Selenium, Gatling, Locust, and reporting integrations.

It also demonstrates the split between package ecosystems: Homebrew carries the command for convenience, while Python packaging remains the upstream's primary installation path.

Timeline

• 2010s: Taurus grows as BlazeMeter's open-source continuous-testing CLI.
• 2016: Early public 1.x tags such as 1.0.0 appear in the upstream repository history.
• 2020s: The gettaurus.org docs describe `bzt` as the command-line tool and document YAML/JSON configuration workflows.
• 2020s: The README continues to recommend PyPI installation while Homebrew packages the CLI for macOS users.

Related projects

• Apache JMeter is Taurus's default and most prominent load-generator integration.
• Gatling, Locust.io, Selenium WebDriver, ApacheBench, k6, Mocha, and JUnit appear in the official documentation as supported executors or workflows.
• BlazeMeter provides the project context and cloud-testing integration.

Sources

• https://gettaurus.org/docs/CommandLine
• https://gettaurus.org/docs/Index
• https://github.com/Blazemeter/taurus/blob/master/README.md
• https://github.com/Blazemeter/taurus/tags