Postman Reviews and Ratings

Use Cases and Deployment Scope

Postman is API testing tool which generates the request (like http) which hits the backend server and get the data from the database. Its a kind of checker between backend and frontend. As, i am in research department which aim to innovate more advanced technology and increasing functionality and reliability.

Likelihood to Recommend

Overall, Postman is the best API testing software with which you can assemble tasks easily, supporting multiple kinds of protocols with huge users across many platforms, such as Mac, Windows, Linux, and has collaborative features and authentication-based features, but is less appropriate for advanced APIs and a large set of data collections.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

i love working especially UI/UX and their courses which they offer to learn more about it. I personally store all the information there.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.