JMeter

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.

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.

It is used to assess websites' performance to find performance issues and in load and stress testing to assess the break point of our systems, it has been used with my department only and by all employees in all projects to find those problems and make our systems more reliable.

In my organization, JMeter is mainly used by the quality department to conduct all types of performance tests. The application is very powerful and has many features. The best part is the fact that it's for free. The Application helps us deliver software products that can withstand a huge load of users which results in better customer satisfaction. You can do stress testing, load testing on both Web UI Applications and API WevServices. Also, you can read the test data needed from external Excel CSV file which helps if you want diverse load tests.

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.

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.

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.

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.

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.

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

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.

Jmeter is used by the development team for testing the performance of web APIs.

We used this product to do graphing and on the fly reporting. It allows us to pull data and graph it without laying it out carefully every time and allows for quick information. We don't use it often but I have enjoyed being able to look at data in a graphic content.

Jmeter is used within our department for REST API Functional and non-functional test automation. It is fast and reliable and quite extensible, that's why we are using it. A single testing module can be made and very highly paramterized such that it would be executed many times with various parameters combinations. It is also easily integrated with Jenkins as a CI framework.

It is used for performance testing of mobile or desktop applications to check the scalability, reliability, and responsiveness of the product in the market. It is used by the performance center of excellence department inside the performance engineering team of the company. It addresses response time issues and performance metrics of applications faced by the client product.

We used JMeter to execute performance tests on our web services. The main business purpose was to assure that changes did not affect web service performance.

We use JMeter to test our platform application. It is used by the whole organization.

I am using JMeter for API testing. I designed a data-driven API testing framework with JMeter, which is very helpful for testing APIs as well as setting up some performance tests. I integrate JMeter with Jenkins. It helps our company a lot for performing and managing the API test. And it is easy to set up a performance test system. I have helped my company set up a lab with continuous load testing to measure the performance of our product, as well as setting up an automation performance testing system and shipped it to some of our customers.

We are doing test cloud-based applications with Apache JMeter. This is used only by my team and not across the organization.

JMeter is used in our department as a performance testing tool. We use it to simulate multiple user systems and evaluate our product's performance.

We use JMeter in our company to test load and performance of our web sites. Our scripts leverage the flexibility and ease of use of JMeter to test the different pages of our websites and generate dynamic content requests. We hired the services of BlazeMeter to leverage their infrastructure to run the test in different regions and different concurrent user configurations to our different regional pages.

JMeter is currently being utilized in our department for streaming and e-commerce applications. I use JMeter for functional, regression and performance testing. We heavily rely on this tool for every release we do to perform the above types of testing.

In our company we use JMeter for our regression tests, also for simple cases such as sign up, log in, etc. It helps us to save a lot of time for some testing cases that should be done every day, so we have created some tests and are running them daily. In our IT company this tool is used mostly by QA team.
Sometimes it helps us to find problems that we could miss. So I hope to work with JMeter as long as it is possible :)
Best Regards,
Narine.

We use JMeter for performance testing of web applications. Presently it is being used by the performance testing team. It is mostly used for analysis of page load response time.