Apache JMeter Reviews

We normally use it for testing APIs or scenarios where the user load is very low. We use JMeter for performing online UI performance test execution, particularly for conditions involving only HTTP or HTTPS protocols. 

It's employed predominantly for executing tests on hundreds to a few hundred users. We also use JMeter in our CI/CD integration suite, where it automatically triggers tests when a new build is generated.

JMeter can be integrated with most open-source platforms like Grafana, Prometheus, or even with custom-made tools by extending it and integrating from GitHub. It supports generating comprehensive reports with numerous listeners. 

Although we don't utilize all the listeners, JMeter provides diverse reporting capabilities that we can leverage. Furthermore, JMeter facilitates scripting capabilities, which include options for Groovy scripts.

I work with Apache JMeter for multiple projects that are currently running in Standard Chartered Bank. We have integrated Apache JMeter with Jenkins and for other purposes, such as executing testing performance center. We have added several plugins and we are using Apache JMeter for our load test executions.

My usual use cases for Apache JMeter primarily include testing APIs and banking services, such as debit and credit card transaction details and getting other services.

I have found valuable features in Apache JMeter such as the JDBC connections for database connections, and the ability to add more plugins to monitor UI aspects. We can add a large number of listeners that are freely available, and the multiple thread groups allow us to mimic real-time production scenarios with virtual users.

Apache JMeter helps my testing analysis by providing precise reports; the HTML format report gives me the exact transactions, response times, and graphs that show average response times, as well as throughput per second. These graphs help customers understand the behavior of the application.

The primary use case for Apache JMeter is performance testing. We use it to test the performance of applications.

Apache JMeter offers plugins for reporting and preparing test scenarios. It allows recording to customization, letting you download plugins to connect with databases or external systems. Despite being open source, it offers features comparable to paid tools, and its ability to customize and expand is particularly useful. Additionally, its open-source nature makes it cost-effective.

I use Apache JMeter for performance testing of web applications. Specifically, I have automated the complete API cycles for performance testing and backend functionality testing. I also generate reports to evaluate the performance of an application, such as download times. Furthermore, I use it for sending end-to-end messages in banking systems and for UI automation.

The valuable features of Apache JMeter include its ability to automate complete API cycles for performance, perform API backend functionality testing, and generate reports that evaluate the performance of applications. It is also adept at handling end-to-end messaging in banking systems and offers UI automation capabilities. I find it highly valuable for these purposes.

I worked on the performance setting of my product, which is a product with an easy UI element that can be added in. People without forward knowledge will be able to easily understand the tool and use it right away.

Other cloud-based performance tools will allow you to view what's going on during the test. However, with this product, it's not possible to monitor live during a test, such as with BlazeMeter, which is very user-friendly.

We are using JMeter for load testing and UI performance testing in both GUI and non-GUI modes. We mainly use it for performance testing and rendering purposes across various projects.

With JMeter, we can execute load tests and generate reports quickly in our CI/CD pipeline, immediately identifying and resolving server and client-side issues before deployment. It effectively scales our testing capabilities without incurring additional costs for increased load.

I mainly used Apache JMeter for manufacturing environments at an enterprise level. One specific use case was where we had to send bulk files via API, which we could not replicate with LoadRunner as it might require additional protocol purchases. With Apache JMeter, we could simulate this scenario, uploading millions of files via API.

There is no significant financial investment as Apache JMeter is a free tool, which helps in scenarios where cost constraints are present.

There is room for improvement in the scripting concepts. The scripting and even the results and reports were very elaborative and informative in LoadRunner, but not in JMeter because everything has to be done manually. 

And, whichever metric we need, we need to add it manually and start monitoring it, but not in LoadRunner. It was a very elaborate report. A lot more information, but not in JMeter.