Postman Enterprise Reviews

I'm using Postman for manual testing of REST APIs. There are some built-in collections done by some of my teammates, so I use those.

The solution is deployed on a public cloud.

I have used some parameterization from a global variable, so that was working fine for me. It's easy to see different versions of responses. There's also a possibility for automation.

We cannot do database connections from Postman directly, and we don't have a way to do that. If they could implement auto-validations and assertions from SoapUI, that would be a very good feature.

We don't have a provision to go and connect to the database from Postman. That's one drawback. If you want to automate in Postman, there is a major drawback. Being a tester, you always want to cross-verify your data with the database. If the database is not connected, then part of your testing becomes manual.

I have used this solution for about seven years.

It's stable. Sometimes it has gone off, and I have had to rebuild the collections again. I've had to switch the logins sometimes. It has crashed twice, and I lost my suites and had to build it again.

Initial setup is easy. Sometimes we get the proxy errors, but when we go to the settings and disable the proxy things, it's pretty simple. Comparatively, SoapUI is easier for me.

Maybe some people who don't have a licensed version of Postman or ReadyAPI might feel that it's easier to automate with Postman, but I'm not sure about that because I haven't done it.

I would rate this solution as four out of ten.

If you don't have SoapUI or if you don't know about SoapUI, then of course you can use it. If you want to explore Postman, it's a free tool.

Postman is a scripting tool.

I started using the solution when we did an SDN-based network implementation from Cisco. I got introduced to a particular scripting tool where I could actually put down everything in an Excel sheet. And if I want to configure, for example, ten ports, then I can actually do the configuration of everything in an Excel sheet. I can pass my credentials in Postman, and I can import the SQL script, and based on whether it's an infrastructure script or a configuration script, I can actually save it in Postman.

I'm using Postman to only push the scripts into the ACI, and that is a very limited use of Postman that we do right now.

I'm sure it might have other usages. That said, we have not explored other features beyond that at this point in time.

The initial setup is easy.

The solution is stable.

It is very user-friendly and has a nice UI.

My limited use of Postman has been to get the output of scripting in Postman or get the output from APIs and then open it in Postman or post the script. We don't use it much beyond that and therefore haven't really explored the features. It's hard to say what is lacking.

Postman does not have a check-in balance. Essentially what I mean by that is if there is something that is already configured on a particular device, it just overrides it without checking whether you really want to override it or not. Even if it is by mistake, if there is a dialogue box that is available before it overrides, it's just a much nicer feature to be notified if you're doing something by mistake.

I've been using the solution for a while. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. We haven't faced any issues.

I know that our team, which is three people, uses the solution. I'm not sure who else does in the company. We're all engineers. 

We have received all of the support we required. Postman has a very good team.

We use quite a few products from an infrastructure point of view. We use SolarWinds, both for server and infrastructure capacity, and we use a change management and a problem management tool. From a bandwidth monitoring perspective, we use a network analyzer; we use Splunk heavily. We do a lot of scripting tools using Postman and Python.

I'm more into Python since Python gives us many more API interjections and compatibility with a lot of other APIs. We started using Postman, and then we immediately moved to Python-based scripting.

The functionality that Python gives you concerning the available APIs and then the ability to put that in the Excel sheet is much better than Postman.

The solution is very easy to set up. There were no issues. 

I don't deal with the licensing aspect of the product. 

We looked into other solutions. However, Cisco actually recommended Postman, so we went with this product. 

I'm an end-user.

I'm not sure which version of the solution I'm using. 

New users need to watch a few videos and understand the solution pretty well. If you are using Postman for the first time, never use the administrative credentials. It is very easy for you if you're using the administrative credentials to pass through the Postman's scripts. It is possible that you might override the configuration unknowingly. If that happens, that can actually bring down a good amount of your configuration or an earlier configuration. It's best to actually get the solution into a development environment before you actually do anything on production.

I'd rate the solution seven out of ten. It's a good, very user-friendly scripting tool. Anybody can learn it and start using it. However, new users do need a little bit of knowledge and must be willing to learn as they go.

Postman is a good tool for completing a sanity check or smoke test of REST APIs. It's a quick way to manage your REST API-related test cases, and it gives good options for assertions for the response of the APIs. We have 30 people using this solution in our business. 

Postman uses the DRY framework of JavaScript and that framework is easy and a good way to put assertions on responses.

Postman could be improved by providing options for performance testing of APIs. We would like to complete performance testing of a specific set of API's by checking them against thousands of the records and checking responses times.

I have been using this solution for six years. 

This is a stable solution. 

This is a scalable solution.

The initial setup is straightforward and only takes a few minutes. 

I would rate this solution an eight out of ten. 

We use this solution for manual API testing, which we call penetration testing. Postman provides a user friendly interface that can be used by non-technical team members. 

It is easy and simple to use and install. It is compatible with Linux, Mac or Windows. Postman is a great solution and resource for those who are new to technical platforms in terms of API development and testing. Postman is an open source solution and so is an affordable resource for those wanting to learn. 

I would like to have a code snippet where I can write a code and for the responses of the endpoints to be validated using my custom business conditions. In certain scenarios, we want to have custom business scenarios and not generic ones. 

We would like to have a code interpreter in Postman and also for automation to be less complex. My team want various complex automations using APIs depending upon their complex business conditions but automation using Postman is limited.

The UI of Postman could be enhanced by adding a proper panel or code. 

I have been using this solution for five years. 

This is a stable solution but user rights can be complicated and cause disruptions. 

This is a scalable solution but scaling it can be complex. 

For support, we use the open communities and documentation provided.

The initial setup is very straightforward.

This is an open source solution.

I have previously worked in the airline industry and used ReadyAPI. This is a licensed product and was used to ensure GDPR requirements and data privacy policy requirements were met. This solution costs approximately 800 Euros. Postman, on the other hand, is free as it is an open source solution. 

Running test cases using Postman is not as easy as with ReadyAPI. 

I would rate this solution a seven out of ten.

We primarily use the solution for testing and preparation of the base URL which I generated for the first tokenization. I prepare the test suite and the XML or Java core that give the input parameters.

The major role is the pre-requisition of the scripts in Postman - which is mandatory.

We can input parameters into Excel and execute for the application.

We work in many environments, including QA, SAP, production, pre-production, and proof. We use Postman for each and every release.  

Before anything goes to the master branch in GitHub, I'll completely check the code and unit test the complete scripting. I'll execute it one or two times, and once it's stabilized, I'll directly deploy it to the master branch.

The output has been very good.

There are lots of good features. 

Its initial setup is easy, depending on the operating system.

It is stable and reliable. 

The product is not expensive, although there is also the option for open-source, so it can be free to use.

We need better version compatibility. In open-source, the main drawback is when you go to integrate the plugins, it is entirely scripted. Sometimes the scripts aren't scripting.

The execution time should only be two or three seconds. 

We'd like to see some better UI in newer versions. 

I've been using the solution for 11 years.

The solution is stable. Before we deploy, we can check in for the local system. Once it is successful, then we'll go for the server side. That is a good practice to follow.

There are no bugs or glitches. It doesn't crash or freeze. 

We have 13 people using the product. It's just my team using the solution, as we have maintained the SSL certification separately.

I'm already an expert in the product and therefore do not need to contact technical support for help. If I have issues, I can troubleshoot on my own.

We chose this solution based on the project. Typically, the client requests something, and, depending on the client and the project's needs, we'll use what makes sense. We use the best tool for the job. If it happens to be this solution, then we use it. If it's something else, we use something else. 

If a file is in Windows, it is very easy to deploy the product. We can do configurations easily and handle test scripts well. It's all very straightforward.

However, other operating systems may be more difficult. The process varies depending on if you are using Windows, Unbuntu, or Linux, for example. 

Depending on the scripting, the deployment hardly takes 30 seconds to one minute. It'll check for the E2E level in the checkpoints, and how to trigger in the checkpoints.

The solution has both open-source and licensing options. You can pay for monthly licensing. However, that's not always necessary. There are also plugins that are available that we can implement. It's not an expensive product, even if you go for the license. They do have multiple licensing options as well. They have options for freelancers and mid-sized businesses as well as larger businesses. 

We are a Postman partner. 

I've been using an older version of the solution. I'm not on the latest deployment.

I'd advise others that it is important to have project middleware functionality, including for the access level. When I work with clients, I will ask for the certifications of the tool. Once the tool is initiated, 99.9% of the time,  there is no management involvement here. It's signed off on.

I'd rate the solution nine out of ten.

Our company uses the solution for single user regression testing of APIs. For each of our releases, we run a regression report that includes APIs contained in that release. 

We create structure suites by importing API information from swagger links, writing test scripts for APIs, and validating the values in our responses. This process can take some time but completed ignition suites can be reused. 

The solution provides visibility for PDF reports without needing to install plugins. 

Other solutions like JMeter require plugins which is not ideal. 

The solution has some user interface difficulties when conducting environment collections. 

It is important to be careful when storing information to ensure files are secure and not lost. Storing information can be a bit hectic. 

I have been using the solution for one year. 

The solution is stable and provides a good user experience. 

The solution is scalable. 

The initial setup is quite easy because installation automatically sets up collections. 

Our company implemented the solution which requires manually writing the process. 

The solution has a licensing fee which might be prohibitive.

There are open source options that are cost effective and offer API testing such as JMeter. 

If JMeter is too restrictive based on your project, then I suggest moving to the solution. 

We use the solution for attrition and single user testing of APIs. 

We use JMeter for automated API testing and load testing for multiple users. 

The solution requires an awareness of APIs, JSON format, XML format, schema, and Java scripting. 

I rate the solution a nine out of ten. 

Postman is an API regression suite, and we design different workflow center processes. We maintain the Postman tool and add JavaScript applications. Since it is not that robust, like ReadyAPI, we have to write many scripts to support it.

The UI is good. It's appealing and free, and everyone can use it.

Postman needs more advanced data-driven testing. We have to provide the data filter in runtime only. It's not like software, and we can add different data sources. That feature is not in Postman yet.

We have been using Postman for one year.

It is not that stable because the bigger the APIs, the higher the chance of crashes. Also, it takes up a lot of RAM and system memory, so it is not that reliable.

It is scalable, but it takes up a lot of resources. We have 40 users using Postman, mostly from the dev, automation and manual test teams. We use the solution weekly.

Postman has a support center, but they are not responsive. Many issues are still pending. I rate the technical support a six out of ten.

Neutral

You complete some setup processes for an application and have to provide the URL. It is not a complex setup. With a bit of understanding of API, it can be set up. I rate the setup an eight out of ten. There is a dedicated framework team for maintenance comprising about six people. Maintenance is required every three months.

Postman is open-source and free to use. I believe there is a corporate license they add to make it more robust and fast, but everyone mostly uses the free version.

I rate this solution a seven out of ten. You can use Postman if you are a beginner or trying to learn API. Small-scale organizations can also use it because it does not need any license.

Postman is gaining pace because it supports the Google Chrome compatibility rate and plugin support. It is easy to set it up for the testing team. It is a good tool, but it still needs improvement for a scalable API tool.

Regarding advice, there are some secure APIs in different organizations, so it's better to get approval from your manager or architect so that APIs are not exposed. Also, it is important to be cautious about the organization's sensitive data before implementing Postman.

We used Postman to test APIs before implementing them. We used the latest version of Postman, and it was deployed on a private cloud, AWS.

It is one of the important tools in API testing, and it helped out team develop mobile apps. First, it allowed us to understand the working and performance of the APIs so we could know how long it takes to give a response and analyze. Then, if there were any problems, we fixed them and implemented them in the code.

The best thing about Postman is it was very easy to use, and we could test APIs and get immediate results. In addition, we could share all our APIs with our other developers securely.

It is not that easy to use and should have a more improved easy-to-use interface.

It was stable, and there were no issues.

We didn't use any other solution before Postman. A senior developer suggested Postman.

It was straightforward to install. We just downloaded it and used it as a tool for testing our APIs. We had a back-end developer and two mobile developers utilizing this solution.

Its usage depends on how many APIs we have to test. So we had a complete collection of APIs that we tested, and once we tested, everything was ready.

There are no licensing costs, and we used it for free.

I rate this solution a six out of ten because no solution is perfect, and every software has missing features. Postman should consider adding more features in the future.

Regarding advice, don't mix up all the endpoints and organize your collections according to the use case. It will be very helpful for other developers to understand the use of the APIs.

The primary use case for the solution is to test the response accuracy of services that we hit without the UI.

The most valuable feature is that JavaScript can be included as tests. That makes it easier to build an end-to-end API suite and it can be automated.

Integration of the solution towards Bitbucket, BitHub, and CI pipelines is difficult.

I have been using the solution for two years.

The solution is stable.

If used as a stand-alone solution it is easily scalable.

The initial setup is straightforward. You only need to download the solution from the internet and run it. The most complex part of the setup is setting up a proxy if it is required.

I implemented the solution in-house.

Unlike APIs, the solution does not require a license.

I rate the solution seven out of ten.

As a standalone option, it's a fantastic tool, but it's very hard for us to collaborate using the solution.

Our development people use the solution for testing.

The solution is a good tool to try out new APIs that the team is building or any existing APIs. It is relatively easier to build out scripts and automate certain flows. The solution as a standalone tool is beneficial in creating utility scripts. 

We use Postman for API testing only. We test it locally and share contracts with other teams. We also enter environmental variables to test different environments.

The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages. I can deploy it locally and QA everything in different environments. 

I can copy the cURL request from the browser when browsing any website, copy the network tab from the browser and import it to Postman instead of rewriting everything, which comes in handy when debugging. If I'm working with a complete browser-deployed app, I can open a specific URL and see the recursion. 

One area that could be better is collection management. I duplicate collections and end up with lots of them. Maybe I'm not using it properly. But a better way to manage and save collections would be an improvement.

Another improvement would be the ability to clone a collection (or even have cloning as the default) to avoid time-consuming production issues.

We've been using the product for three or four years.

Postman is pretty reliable. I haven't encountered many stability problems.

Only the client can test it. I do not see much use for scalability. For example, if I have all these collections, I can use some script and automate the flow. Other than that, we don't see many use cases for Postman itself. 

So far, we've had no issues with Postman that required support because we just make an HTTP call and show the results. So we can get all the support we might need from sites like Stack Overflow.

Positive

The initial setup was straightforward with a little complexity.

Implementation was done in-house only.

We tried some different solutions after using Postman, not before. But Postman has better graphical support than its peers. At that time, I tried using a product whose name I can't remember ("Fire" something, I think) and others but had problems with them, so stopped.

I would rate this solution eight out of 10.

Regarding our relationship with the vendor, as far as I'm aware, the company has no business relationship with Postman. We use the product because it's the world's most commonly used open-source tool for repair testing.  

Regarding the number of staff required for the daily maintenance of the solution, we only make changes when the Postman tool or the contract changes. API contracts are modified daily. Most staff members continually modify or update these collections. Our developers use Postman at least once a day when developing.

My advice for others looking to implement Postman in their companies is that there is no reason to implement Postman. Plenty of other solutions are available, but most people are familiar with Postman because it appears in several YouTube tutorials.