Installer jmeter avec Homebrew, chocolatey, apt, MacPorts, Nix, scoop, winget

Liens du projet

• Page d'accueil
• Page du gestionnaire de paquets

Commandes et alias

• jmeter

Historique du projet

JMeter's public change history reaches back to early 1999, with version 1.1 in February, version 1.2 in March, version 1.3 in April, and Apache JMeter 1.4 in July. Those entries show a young Java GUI tool gaining URL aliasing, cookie handling, HTTP authentication, visualizers, POST fixes, and command-line argument fixes.

By version 1.5, JMeter had abstracted the sampler model, added thread groups, and gained save/load support for test samples, setting up the architecture that made non-HTTP testing possible. The Apache homepage later summarized that direction as expansion from web-application testing into broader static, dynamic, server, network, and protocol performance testing.

The long 2.x and 3.x series turned JMeter into a general load-testing platform. The change history records additions and refinements across Java integration, JDBC, JMS, samplers, listeners, distributed testing, scripting, logging, and reporting. Version 3.0 bundled Apache Groovy for JVM scripting, showing JMeter's shift toward scriptable, extensible test plans.

The 4.x and 5.x series kept JMeter relevant for automated performance testing: the user manual and best-practices pages emphasize GUI mode for building test plans and CLI mode for load execution, distributed or multi-instance runs for larger tests, and careful listener choices to avoid distorting load results.

Historique d'adoption

JMeter is widely packaged because it is a mature Apache tool with a stable command-line entry point and a cross-platform Java runtime model. The input package metadata records Homebrew, Chocolatey, Debian, Ubuntu, MacPorts, Nix, Scoop, and Winget packaging.

Its adoption also comes from the `.jmx` test-plan format and CI-friendly CLI mode: teams can build or record plans in the GUI, then run them repeatedly from scripts, build pipelines, or distributed controller/worker setups.

Modes d'utilisation

A common JMeter workflow is to build a test plan in GUI mode, using recording or manual samplers, then execute load tests in CLI mode with commands such as `jmeter -n -t test.jmx -l test.jtl`. The best-practices guide recommends CLI mode for load and warns against heavyweight result-tree listeners during load runs.

JMeter can test static and dynamic resources and many server/protocol types. Its manual organizes it around test plans, samplers, thread groups, listeners, functions, properties, distributed testing, recording, and component references.

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

For package nerds, JMeter is the heavyweight Java CLI/GUI hybrid that anchors open-source load testing in package managers. It is not a small Unix filter, but it still behaves like a packageable developer tool: install it, run `jmeter`, keep test plans as files, and execute load runs from scripts.

Its significance is historical as well as practical: few developer-tools packages have a public change log spanning from Java 1.x-era web testing through modern CI performance testing while staying under the Apache project umbrella.

Chronologie

• 1999: Version 1.1, 1.2, 1.3, and Apache JMeter 1.4 appear in the change history.
• 2000: Version 1.5 abstracts samplers, sampler controllers, and test samples, and adds thread groups plus save/load support.
• 2010: The Apache GitHub mirror repository is created.
• 2016: Version 3.0 bundles Apache Groovy for JVM scripting.
• 2018: Version 4.0 appears in the 4.x line.
• 2018: Version 5.0 begins the 5.x line.
• 2026: The Apache changes page records 5.6.3 and notes Java 8 execution support with Java 17 recommended.

Related projects

• JMeter belongs with Apache performance and testing infrastructure, Java application-monitoring tooling, and load generators. The documentation also connects it to distributed testing setups, JUnit samplers, access-log samplers, and plugin/extensibility work.

Sources

• Apache JMeter homepage, user manual, best-practices guide, change history, changes page, GitHub repository metadata, and Homebrew formula metadata.