Apache JMeter
Last updated
Was this helpful?
Last updated
Was this helpful?
Apache JMeter is an open-source tool designed to test the performance and load of web applications and other services. It is widely used for simulating heavy loads on servers, networks, or objects to analyze performance and measure system behavior under stress.
Purpose: Originally designed for testing web applications, it now also supports testing of a variety of protocols including HTTP, FTP, TCP, JDBC, JMS, and more.
Platform: Built on Java, JMeter is platform-independent and can run on any OS with a Java Runtime Environment (JRE).
JMeter requires Java (at least JDK 8 or later). MacOS usually comes with a version of Java preinstalled, but you can check and install the latest version if needed.
Open terminal and run:
If Java is installed, it will show the version. If not, install it.
Use Homebrew (recommended):
Once installed, set up the environment variables:
Verify installation:
Visit the Apache JMeter website.
Click on the "Download" menu and choose the latest .tgz binary version for JMeter.
Direct link for binaries: JMeter Download.
Alternatively, we can use the terminal curl command
Replace {VERSION} with the latest version number, e.g., 5.6.2.
Navigate to the folder where the .tgz file is downloaded and extract it:
This will create a folder named apache-jmeter-{VERSION}.
Navigate to the JMeter directory:
Launch JMeter:
JMeter will launch the graphical user interface (GUI) on Mac.
To simplify running JMeter from anywhere in the terminal, we can add it to our system's PATH:
Open .zshrc file in a text editor:
Add the following line:
Replace /path/to/apache-jmeter-{VERSION} with the actual path to your extracted JMeter folder.
Save the file and reload the shell configuration:
Now we can simply type jmeter in the terminal to launch JMeter.
Run the following command in terminal to verify JMeter is installed:
This should display the JMeter version.
HTTP, HTTPS (web applications)
FTP (file transfers)
JDBC (database testing)
LDAP (directory services)
JMS (Java Messaging Services)
TCP/IP, SMTP, POP3, IMAP (mail servers)
SOAP/REST Web Services, MQTT (IoT testing)
Load Testing: Simulating concurrent users to analyze system capacity.
Stress Testing: Testing the system under extreme conditions.
Performance Testing: Measuring response times and resource utilization.
Regression Testing: Repeating tests to verify system stability after changes.
Supports plugins to enhance functionality.
Allows scripting via BeanShell, JSR223 (Groovy), and Java for advanced customization.
A user-friendly GUI makes it easy to design and debug test plans.
Provides rich reporting features (graphs, tables, and dashboards).
Supports testing across multiple systems to simulate large-scale load scenarios.
Monitors resource usage (CPU, memory) during tests.
Collects system performance metrics using listeners.
Works with CI/CD tools like Jenkins, Maven, and Docker for automated testing pipelines.
Blueprint for the testing process.
Contains test elements like Thread Groups, Samplers, and Listeners.
Simulates multiple users by creating threads.
Configurable parameters include the number of threads (users), ramp-up time, and loop count.
Generate requests to servers.
Types include HTTP Request, FTP Request, JDBC Request, SOAP/XML-RPC Request, and more.
Logic Controllers: Define the flow of test execution (e.g., If, Loop, Switch).
Test Fragment: Reusable pieces of a test plan.
Collects test results and provides visual reports.
Examples: Graph Results, Summary Report, Aggregate Report.
Validates responses to ensure expected results (e.g., Response Code, Text Matching).
Adds delay between requests to mimic real-world scenarios.
Prepares configuration details (e.g., HTTP Request Defaults, User Defined Variables).
Pre-Processors: Modify requests before they are sent (e.g., URL Rewrite).
Post-Processors: Extract information from responses (e.g., Regular Expression Extractor).
High Resource Usage:
JMeter can consume significant memory and CPU when handling large tests.
Distributed testing is recommended for heavy loads.
Lack of Browser-Based Testing:
JMeter does not simulate browser behavior (e.g., rendering, JavaScript execution).
Use Selenium integration for this purpose.
Steep Learning Curve:
Advanced features require knowledge of scripting and performance testing concepts.
Limited Real-World Simulation:
Cannot perfectly mimic real user behavior without additional customization.
Load Testing a Website:
Configure Thread Group for 100 users.
Use HTTP Sampler for GET and POST requests.
Add listeners for detailed metrics.
Database Load Testing:
Use JDBC Request to query the database.
Simulate concurrent database connections.
API Testing:
Parameterize API requests with CSV Data Config.
Validate responses using JSON Extractors and Assertions.
Distributed Load Testing:
Set up master-slave architecture to run tests across multiple systems.
