JMeter is well suited for Java applications where the user can script the scenario once and make changes to accommodate for as many numbers of users for load test execution. The image and selection of any files or exporting files scenario is handled well.
It is less appropriate to test Ajax applications where it is required to script click per use.
IF you are looking for api testing solution along with service virtualization, then look no further than this tool. This tool also forces you to move your testing lifecycle to much earlier phases of development which helps overall SDLC.
Easy of use - in generate load like HTTP requests, and processing/analyzing the responses. No coding is necessary at the basic level, just need to understand load testing and the infrastructure being tested.
Automatic management of things like cookies to help with session state support - so you don't specifically have to worry about it or handle it
Lots of testing/configuration options to suit your needs in making the right load generation (sampling requests), and analyzing the results, including any pre and post processing of the results first. Things like the Beanshell/BSF pre/post processors, response assertion, regular expression extractor, XPath extractor, CSV data set config
There is a JMeter cloud service called BlazeMeter that I think would be useful for those that need to scale up high load without provisioning their own systems. I've not personally tried it though, but I recently attended a meetup presentation that highlighted nice useful features that BlazeMeter provides. One should evaluate the service if they are considering JMeter and need to expand beyond existing hardware resources.
It immensely helps to change your entire testing lifecycle approach and to implement Shift Left approach with the extensive emphasis on testing the api's.
This is a great tool to implement Service virtualization for your and/or third-party web services. This will ensure we have 100% environment availability and consistency for automation and performance test environments.
This tool also helps you with test data setup and management which is a very crucial piece of test automation.
It also helps us to implement performance testing for apis using the Blazemeter.
Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.
This tool comes with a license cost and not free. Many open source tools offer free api testing solution and so making some functionality of this tool as open source would be good
Load testing piece is not integrated with in the tool and rather uses Blaze meter which is free.
Some integration with UI and api testing will make this tool even more attractive
Price, Wiki and user sharing. Having access to the information provided by the developers and other open source providers is key for me. The ability to share information and get answers directly is very important to success in software testing. And the price of this product currently is amazing. Too many companies charge way too much money for products that are far behind in their value and pertinence
I can jump right into a new test plan and start building from scratch. The natural progression from test plan to thread group and then designing the basic format of the process is very streamlined and smooth. With only slight modifications I can build out a very complex model from a very basic beginning.
I have been using JMeter for the last year. By using this tool, you can make sure the system will work under varied loads. It helps us to simulate real time scenarios by creating required virtual users and make sure the application will work under load. Perform load, stress, and stability testing using JMeter.
I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them (takes a while) and setup tests and firewalls, etc.
It definitely is among the top leaders in API testing and virtualization along with the Parasoft SOA tool. Many open source API testing libraries such as Rest Assured, Karate and even Postman and SOAP UI are free which is a little bit against CA.
This tool gave a very positive ROI in our group. Especially with service virtualization where we minimized the downtime in our test environments significantly.
Also, service virtualization helps to minimize the costs of hitting third party services often in lower environments.
