JMeter Reviews & Insights

Apache JMeter helps ensure our performance targets are met for release, and quantifies changes we make in the name of performance. Without it, we end up with custom code written by system testers or QA that don't always fully understand how code evolves, and then inevitably we have to throw it away in a year. Apache JMeter allows developers to run standardized performance tests ahead of QA.

For local, simple systems (think, "it has a main and it goes from there") it will do 10/10. Even for common frameworks, it can instrument/monitor/measure very accurately out of the box; we have even had some attempts at hitting it against a user interface, although then the developer must know more about some internals to understand what is being measured. Strong recommend for data processing code - that is, code that is repeatedly invoked.

Apache JMeter helps our team in areas like load testing and performance benchmarking of APIs across products and services. Every new feature that gets released is the first load tested using Apahe JMeter, by passing appropriate parameters to check if it can handle the list and stress easily. This helps to assert that the service can easily serve 'x' users in 'y' conditions. With teams focusing more on microservices and agile development, non-functional testing plays a vital role. Apache JMeter is an open-source tool written in pure Java, making it the most preferable option for us to test our services, both API and UI through its user interface as well as Non-GUI mode. This makes the SDET team perform testing and feature releases more confidently with optimum quality.

Best suited:
Any new service i.e. monolith or microservice must be load tested to check how it can scale at extreme load, this helps to be prepared early and stay ahead of the competition too.
Not suited:
Limited CPU and Memory resources are available.

Jmeter is used for the load or performance testing of an application. It is used to identify the bottleneck in the performance and improve the user experience. We have used for newly created authenticated API, Identify management system, and database to store PII. It is worth the tool to create your project and scripts to benchmark the performance numbers for future releases and improvements. We have found many bottlenecks in the application which required to re-design the data flow with the help of Jmeter.

Performance testing of API, UI, Back-end, Middle layer of an application which transforms the data and consumer application uses it to Scale your tests to any size. Run Your Existing JMeter Tests At Any Limit From Any Location. Continuous Load Testing. Services: Scale your load testing. For any new API, it is better to benchmark the performance numbers for future improvements.

JMeter is used by both software developers and testers to check that the application functions correctly. It's used in 2 ways: check that the new version of the application functions as expected and also for load testing the application. After the tests are written once by a software developer they can be automated or easily run manually by a non-technical person.

JMeter is designed to perform load tests against web applications and suits this purpose well. It is a completely free application and runs on multiple platforms without any hassle. It can also be used to check that the new version of the application functions correctly (regression testing), however, JMeter doesn't actually run the application in the browser but only checks for server responses. The benefit of this is that it requires a lot fewer resources & setup, the drawback is that more complex tests that require lots of UI interaction may not be possible.

We used JMeter for performance and load testing of our cloud service to verify that it worked well with many users before launch and also to be able to calculate costs when scaling up the service for more users.

It’s great for load testing when you want to apply a load but wants to be sure it’s not restricted by the client machine you run JMeter on. It can be a bit hard to use for people without Java skills.

Apache Jmeter scripts are great for load testing. I like the parameterization strategy offered by JMeter because I can better reproduce real-life scenarios by introducing variables and randomizing my tests. Also, JMeter extensions are accessible in the open-source sector to extend current JMeter capabilities. I love this to do my performance testing.

Apache Jmeter is very useful for parameterizing tests and loading info, which means it has a great performance testing. JMeter will allow you to evaluate if you need to extend outside the existing hardware infrastructure. It can maximize the access to the CSV data by reading it correctly, as the I/O efficiency is overhead. It also offers a very simple user experience, many plug-in modules and a range of graphical maps and descriptive notes to the audience. You could even use the chrome BlazeMeter add-on to capture, retrieve, and create JMSX files in HTML Cookie Manager for an app-based check.

Most of our developers use JMeter for performance testing. It's a great tool where you can do all kinds of performance testing tests like Baseline test, smoke test, load test, and stress test. It is useful for test performance and scalability of REST APIs. It is used as an automation tool for API testing.

It is a very great tool for running load tests to check the performance and scalability of REST APIs. Its free for commercial use and well supported by the community. It needs to have a very good system that supports a high heap size. It has a lot of plugins and extensions which can improve performance testing.

JMeter is being used by our QA teams mainly for performance testing. We are into banking and finance domain. Hence, the performance of the bank transactions should be very rich. JMeter helps us to find bottlenecks around performance issues within our web apps and web services. JMeter also helps us to simulate different user loads in order to test web application under various load patterns.

It is well suited for the organization who is looking for an open source solution for their performance testing needs. JMeter is the best tool for performance testing, I don't see any limitations here, and hence it's never less appropriate for any organization.

JMeter is being used to run load tests against the web applications that we are working on.

It's useful to test web applications and verify that they are working as expected. It's not the best option if you want to work on the scripts to modify them because the scripts are huge.

JMeter is the main preferred performance testing tool in my organization. It is the best tool to test the performance of an application at the protocol level and also at the UI layer with various thread groups, listeners etc.. The blazemeter plugin for record and playback is also very helpful. Jmeter itself has a very neat UI. It being an open source tool makes it more and more attractive.

If you are looking for Open source or even starting off with performance testing, JMeter is the tool for you. The more you use JMeter the more you will learn it's powerful capabilities. It's best suited for testing the API layer/protocol layer. You can also achieve UI layer performance testing with selenium samplers.It has powerful assertions and so you can use JMeter as functional test tool too at the service layer. Parameterization is very easy. Html cookie manager will help you immensely for a browser-based test. You can use a blazemeter plugin on chrome for record.playback and JMX file creation.Jmeter is not recommended when you want to test the performance of the application with complex scenarios in UI layer.