macOS
Homebrewverified · 100%
brew install bztlocal Homebrew formula metadata
brew / rank 3120
Install bzt with Homebrew
BlazeMeter Taurus. Version 1.16.51 via Homebrew; verified 2026-06-20.
install
Additional install commands
overview
Package summary
BlazeMeter Taurus
Project links
Commands and aliases
- bzt
- jmx2yaml
- soapui2yaml
- swagger2yaml
history
Project history and usage
Taurus, installed as the `bzt` command, is BlazeMeter's open-source automation-friendly framework for continuous testing. It wraps tools such as JMeter, Gatling, Locust, Selenium WebDriver, and others behind a YAML/JSON configuration model.
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
security posture
No protected-tool coverage found yet
No matching local secret-handling manifest was found for bzt. Nucleus package metadata is still published here so future coverage has a stable package URL.
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
/etc/bzt.d~/.bzt-rc
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.bzt-rc
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
bzt | executable | indexed executable | Discovered from the local executable index. |
jmx2yaml | executable | indexed executable | Discovered from the local executable index. |
soapui2yaml | executable | indexed executable | Discovered from the local executable index. |
swagger2yaml | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.16.51
manager updated2026-06-20
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:bzt |
|---|---|
| Version | 1.16.51 |
| Package manager | Homebrew |
| Homepage | https://gettaurus.org/ |
| Repository | https://github.com/Blazemeter/taurus |
| Last updated | 2026-06-20T10:32:09Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- pkg.so package database
- pkgdb category and tag curation