Fast API calls: Many users have found the fast API calls feature to be very useful for HTTP protocol and restful service testing, with several reviewers mentioning its efficiency and time-saving capabilities.
Free and open-source tool: The fact that the software is a free and open-source tool has added to its appeal, as mentioned by multiple users. They appreciate the accessibility and affordability of the software.
Collaboration features: Several users have appreciated the ability to share API connections, create collections of API calls, and collaborate seamlessly with teammates. This universal feature of the software has been praised for enhancing teamwork and facilitating collaboration regardless of location.
Postman is really great and one of a kind tool for all our API's. We have all the API's there and working with it is really great.
i love working especially UI/UX and their courses which they offer to learn more about it. I personally store all the information there.
In our current business in my organization, we are moving from a legacy system to a new system with the latest cloud technology, and since everything is new, we are testing from scratch. Here, postman plays an important role in API testing. Managing collection through Postman is so easy that it makes testing comfortable.
So, one of the significant and essential use cases for API is to test RESTful APIs during development; this gives early feedback in agile development without more test setups. It also supports writing test scripts in JavaScript to validate response data (status codes, headers, body). Mocking is also provided by API, which is important in agile development.
Postman helps us not only use APIs, but to save setups, workspaces, preferences, etc. This means we can adopt 'personas' when interacting with an API to test various use cases where certain permissions or roles are being used. Being able to share these workspaces and templates means people can publish and pull a standard setup for each type of API we work with.
Postman is good for organising your API credentials, vendor settings, environments etc. It's also a good way of getting stared with APIs as you get to use a GUI which can help you understand what we mean by a 'body' or 'bearer token'. I think people generally gravitate towards GUI tools for getting started in a new technology area.
Postman just solves all the problem that developers had with the uses of API builidng and testing. It is baically an end to end solution for API. We can build and test it. Earlier it was so difficult to debug an API and now it is so easy. Earlier we had to write code and send the request and then see the response and then debug but with the development of this app, it has become so easy. It is saving a lot of engineering hours and I will recommend all Organizations to use it.
It is well suited for all engineering scenarios. Any engineering organization which has API in use should use this without any hesitation. If you are building an API ? use it. If you are testing an API ? use it. If you are debugging an API ? use it. Use it for an end to end API development.
We use Postman to test and automate any new API's that we are creating, we have created full suites of automated scripts, which has allowed us to speed up testing in key areas. It also allows developers to run a test when needed to improve the quality of the overall work while at the same time reducing the time needed to test things.
Postman is easily one of the best tools for API testing, there is a lot to it and best of all there is a free version of the software, you can build out security test's as well as long as you know what you are doing with it, the only thing I can think of where it might not be appropriate is if you are not doing anything with API's. It doesn't allow any testing of any UI, just API's, so you will still need other tools to ensure full coverage.
The regular use case Postman is fine as it's helpful to manage multiple APIs belonging to various projects. but for our case, Postman is a big relief, especially because we often have to communicate with non-conventional clients who have their own custom API-consuming mechanisms. i.e SAP service; those guys do not possess familiarity with convention REST APIs. this is where Postman proved to be a big help. all we needed from our side was just give a link and they'll get the whole API collection.
if you have a small number of APIs to work with, it's probably an overkill
it is very efficient when it comes to manage large number of APIs, one can manage APIs per project as well.
very good authentication testing UI. makes it pretty easy to work with all kinds of available AUTH practices.
allows to ingest multiple types of data like FORMDATA/JSON
Postman is what we use to test our API systems. We have a variety of public and private API systems, all of which are tested by my team using Postman. We've created separate collections for each, such as Smoke tests, which we run at each test deployment and Functional tests. These tests are continually updated (collection). My issue is that it lacks database connectivity, either relational or trendy-document databases like MongoDB. I have no choice but to export data from these databases and feed it into Postman. This is the only manual step a user must take; the rest of our tests are entirely automated.
When dealing with a collection of requests, it's common to run them in the order they were received. Other times, skipping or repeating certain requests is beneficial. The mailman arrives. The method SetNextRequest. You can programmatically choose which requests run and in what order by using conditional logic in the Pre-request or Tests tabs.
We're using Postman for testing of our API systems. We've got many different API systems, public and private, and all those systems are tested by my team using Postman. We've created different collections for each, as Smoke tests, that we run at each test-deploy and then we also have Functional tests collection. We're continuously maintaining these tests (collection). The problem I've is that it lacks the connectivity with databases, either relation or trendy-document DB like MongoDB/ CosmosDB. I have to rely on exporting data from these DBs and to feed it in Postman. This is the only manual step a user has to perform, otherwise our tests are based fully on automation.
Postman is well suited where APIs are involved. I've been testing many backend systems and are well organized into many tests like Smoke for each system and then functional tests as well. Along with that I've few created monitors for production-critical endpoints/API-methods.
Postman is less appropriate where you need to automate your tests that involves verification from databases or depends on data from databases. Also, it lacks functionality to generate random data. I've been using work around using scripts to achieve randomness in my tests.
Being an IT Company, our organization was in need of an API testing and management tool. It had been a lot of hard to maintain APIs that connect the backend and frontend of our applications. Postman helped our company to manage and test the existing APIs as well as has been helping us to create new APIs. With the help of API documentation feature of Postman, it has been easy to provide guide to our clients within few clicks.
Postman is best suited for the web and application development companies in which we constantly need to create APIs and test them. It is less appropriate for Graphic designing firms, animation companies and other companies that don't need to create APIs.
I am working in the company as a Test Automation Engineer. I am using Postman for testing different services in different environments. I basically use this tool to test REST requests. My job is to test various services for the organization, do regression testing, smoke testing, functional testing, and much more. All of my business problems are addressed by this product. I love the simple, nice UI it has. It is a very useful and user-friendly tool for making API calls. Postman has many features I like. It keeps the history of your last used requests and this helps in re-using those requests if you want to. It also allows you to maintain your own workspace. [Postman] has folders to make your work easy, it's easy to share with your colleagues, and also allows me to save the request info in my local machine. I think the most important feature is it's free to use. Overall, I find this tool very helpful. It's a good platform for user testing services.
Scenarios where [Postman] is best suited: It is best used for making API rest calls. It is easy to use. [Postman] allows you to maintain your own workspace/collection of new or repeated requests. Scenarios where [Postman] is not best suited: Sometimes JSON files are difficult to import, so it needs improvement in that respect. It is not good support for SOAP API calls.