JMeter, from Apache, is a load and performance testing tool.
N/A
Postman
Score 8.7 out of 10
N/A
Postman, headquartered in San Francisco, offers their flagship API development and management free to small teams and independent developers. Higher tiers (Postman Pro and Postman Enterprise) support API management, as well as team collaboration, extended support and other advanced features.
$0
Pricing
Apache JMeter
Postman
Editions & Modules
No answers on this topic
Postman Free Plan
$0.00 US Dollars
Postman Basic Plan
$12 US Dollars
per month per user
Postman Professional Plan
$29 US Dollars
per month per user
Postman Enterprise Plan
$99 US Dollars
per month per user
Offerings
Pricing Offerings
JMeter
Postman
Free Trial
No
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
1. Postman Free plan: Start designing, developing, and testing APIs at no cost for teams of up to three people.
2. Postman Basic plan: Collaborate with your team to design, develop, and test APIs faster; $12/month per user, billed annually
3. Postman Professional plan: Centrally manage the entire API workflow; $29/month per user, billed annually
4. Postman Enterprise plan: Securely manage, organize, and accelerate API-first development at scale; $99/month per user, billed annually
Postman is really more about API testing, and was never aimed at performance/monitoring the way Apache JMeter does. If you find someone trying to use Postman this way... show them the way!
Best open-source performance testing tool. JMeter has no alternative for performance testing. It is really easy to record and enhance scripts using this tool. It provides lots of free plugins which gives us much flexibility. It can be executed using GUI or non-GUI. Good tool …
Postman is a great out-of-the-box tool for API testing. SwaggerHub is also good but requires a bit more configuration to integrate with the API you're going to test (if the API isn't set up for it, you probably won't get much out of SwaggerHub).
Postman has pros and cons both and keeping them in mind we are using multiple tools to leverage our Services, integration, automation, and testing needs.
Some of the above mentioned tools have better automation or complete framework implementation capabilities. Having all the …
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.
Postman is very good for easy entry into testing. Thanks to snippets it is easy to use, but also provides a lot [of] possibilities for testing thanks to the in-line editor. Easy to use on multiple environments (versioning) thanks to sets of environment variables. The Collections view can get very full with time and it is not possible to reuse or link requests so that they have always been copied and maintained manually for each copy if changes have to be applied.
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 has opened a door for me to explore more out of it, as it is associated with so many APIs that I never felt any difficulty in finding the right API template, which are well organized and easily available.
It is very secure to use and provides great services which are user-friendly.
Due to this software I have got rid of the excessive emails and the slack channels, Now I am using my own private API and even it give me an option to produce my personal Postman’s API Builder from its Private API Network and this features has shared my excessive workload.
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.
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 think from a non-technical perspective there are a few things that could be more clearly labeled to better understand what is being asked for or where to add certain parts of the request.
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.
There is a lot of in-depth documentation for Postman available online, including detailed guides with screenshots and videos. They provide example APIs for new users to explore while learning how to use the tool. Generally, bugs in the client are quickly addressed through frequent free updates. Community and professional support options are available - most of the time, the free/community level support is adequate
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.
Previous to using Postman, I would either use browser tools directly, or write an in-house tool to send requests. Postman eliminates that need while providing a much better experience and more features. At the base level, Postman is as simple as typing in the address as you would in a browser. Authentication can be provided simply as well.
Postman is free (although there's a paid tier that offers more features) so using it for testing APIs comes with little to no risk (besides learning curve).
The learning curve is a little steep for non-developer users, but developers should find it easy to pick up and use right out of the box, so to speak.
