Installer artillery avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• artillery

Historique du projet

The public GitHub repository was created in May 2015 under the Artillery organization. GitHub releases show 1.5.x artifacts in May and June 2016, while the current repository has evolved into a monorepo around the `artillery` CLI package.

The project describes itself as cloud-scale load testing. Its README and documentation emphasize distributed execution on AWS Lambda, AWS Fargate, and Azure ACI, protocol support for HTTP, WebSocket, Socket.io, gRPC, Kinesis and more, and an extension/plugin model.

Historique d'adoption

Artillery's adoption path is typical for a developer-first testing tool: npm global installs are the primary documented installation route, while Homebrew packaging gives macOS and Linux package-manager users a native formula. The GitHub repository metadata reported roughly nine thousand stars and hundreds of forks at research time.

The product focus broadened from API load tests into full-stack reliability workflows. Current official docs position Artillery for Playwright E2E testing, scalable load testing, and synthetic monitoring, which helps explain its use by developers, QA engineers, and SREs rather than only dedicated performance-test teams.

Modes d'utilisation

A typical Artillery workflow is to write a small test script with a `config` section, target, phases, and scenarios, then run it from the CLI locally or in CI. The reference docs show YAML and TypeScript test-script forms, and the README points users to examples plus guides for Playwright, distributed load tests, SLO checks, Apdex, and observability publishing.

The package matters in Homebrew because it provides a single `artillery` executable for a tool whose upstream ecosystem is otherwise npm-first. That lets users keep load-testing tooling beside other CLI dependencies managed by the OS package manager.

Pourquoi les passionnés de paquets s'y intéressent

Artillery is interesting to package nerds because it sits at the junction of Node packaging, cloud execution, and ops tooling. It is a CLI with a JavaScript package core, but its value shows up in CI pipelines, observability integrations, and serverless execution targets.

The v2-era repository also shows the modern pattern of developer tools becoming platforms: one installable CLI, a script format, cloud runners, Playwright integration, plugins, and telemetry sinks.

Chronologie

• 2015: Public GitHub repository created.
• 2016: GitHub releases show Artillery 1.5.x builds.
• 2026: Artillery v2.0.33 published according to GitHub Releases.

Related projects

• The official README points to Playwright load testing, distributed runners on AWS Lambda, AWS Fargate and Azure ACI, observability destinations such as Datadog, New Relic and Honeycomb, and community/official integrations.

Sources

• https://api.github.com/repos/artilleryio/artillery
• https://api.github.com/repos/artilleryio/artillery/releases
• https://github.com/artilleryio/artillery
• https://raw.githubusercontent.com/artilleryio/artillery/main/packages/artillery/README.md
• https://www.artillery.io/docs
• https://www.artillery.io/docs/reference/test-script
• source_facts.package-manager