Postman Enterprise Reviews

The primary use case of this solution is for the API manual testing, manual verification to get the response, and for API automation.

The most valuable feature is the user interface because it provides a clear space for the URL, headers, body, prerequisites, and tests.

The solution can be improved by providing detailed error logs including the line the error took place to make it easier to correct. I would like to see functionality added for uploading specific scripts and not the entire collection.

I have been using the solution for three years.

The web app version is more stable than the desktop application.

The solution is scalable.

The support team is very responsive in resolving any issues we have.

Positive

The initial setup is straightforward. 

The solution is free for individuals, but for companies that use it across the organization, you have to pay per user. The solution is competitively priced.

I give the solution ten out of ten.

If you have a small amount of knowledge of HTTP status codes, how to make collections, and how to deal with environment variables is enough to use this solution.

We have 1000 people in our organization using the solution daily.

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.

I use Postman for API testing. I use this solution for UI or automation purposes.

I like that it is very easy to use. I also like the automation feature.

It would be better if we could integrate programming languages like .NET, Java, and JavaScript. It could also be more user-friendly.

I have been using Postman for three to four months.

Postman is a stable product.

Postman is a scalable product. We have two or three users using Postman in our organization.

The initial setup is straightforward because we are IT professionals. 

On a scale from one to five, I would give the initial setup a 5.

I am using the free option.

ReadyAPI is very good, but you have to pay for it. Postman has a free option, and that is why I am using it. ReadyAPI is more user-friendly. For example, its features elaborate on what happened. You can right-click on the thing and add the features. In Postman, we have to find things from the inside and then get it into the project. The main difference with Postman is the ability to connect with different application tools integrated with Jira and database connectivity. 

On a scale from one to ten, I would give Postman a nine.

We use this solution to create multiple automations for a number of different users. 

We have previously used Tosca which allowed us to verify information using authentications. It would be useful if this was also possible using Postman. In a future release, Postman should connect to DB.

This is a stable solution. 

This is a scalable solution. 

The initial setup of this solution is straightforward. Postman can be used as an extension in Google Chrome for those who do not wish to install it directly. Deployment took an hour and a half.

This is a fairly good tool and I would recommend it to others. 

I would rate this solution an eight out of ten. 

When critical things happen, and we need immediate testing, we use Postman or SoapUI.  For example, when testing ServiceNow applications, we use Postman to call the APIs. The data sequence of the APIs has to be called, so we create test cases in Postman that call the appropriate data, authentication keys, and everything else we include in the data. And when we post about it, we include all that data. We fill in all of the required fields and send the request. When we get the response, it will include some data. We capture that and send it along on the subsequent request. So we usually use Postman to keep our directors informed during our integration and product testing. It's a pretty mature solution. Postman is about seven to eight years old. 

Postman has helped up with storing data, sharing test cases, and reporting. It's much easier to share test cases with teammates. I don't have to deliver an Excel sheet with all the test cases in there. It covers my list of requirements. For instance, it gives me the raw data, and if I need a new structure or format, it does everything automatically. Back in 2012, it was a browser-based application that you open in Chrome, but now it's a desktop application. It makes my life much easier. The browser-based app was frustrating because Chrome uses a lot of memory, and the browser often crashed. 

Postman allows you to incorporate and export the test cases we create. It enables me to share the test cases with my colleagues, so I don't have to copy them into an Excel sheet. Postman lets me export the dataset and share it with my team. They can use my test case for their testing. 

It lists all the tests I have done, so I don't have to report them separately. With SoapUI, I can't do that. So every time I run a test case in SoapUI, I have to note in an Excel sheet the data, response times, etc. Postman sets the data free. It records the calls, responses, and everything else I need. So I can create a report and then go back and see what testing happened in the past month. 

Testing API is pretty straightforward in Postman, but it falls short when testing web services. For example, when we test web services, there is a visual component that we can import in SoapUI but not in Postman. It's pretty challenging to work with visuals in Postman, but it's much easier in SoapUI. We used Postman to test web services three years ago, but we found it wasn't suitable, so we started using SoapUI. If Postman's web services testing were smarter, it would be the number one tool we use.

It would be great if Postman could add some more integration with the other testing tools we use. For example, it would be nice if we could create a test case scenario in Postman and execute it using Jenkins during the CFPB pipeline. That would be an outstanding feature that we could use. Writing a lot of code for test cases in Selenium is much more complicated than creating a small test in Postman. So that'll make our life much easier.

I've been working with Postman for the past six years.

Postman is pretty stable. When I was using the browser-based version, it took a while to load. Now it takes a little time but not very much. It's about as fast as any other application. But when I was using the web app in my Chrome browser, the browser would crash, and sometimes my system would freeze. So we had that issue earlier, but the performance has improved a lot.

Postman is scalable. I can have multiple instances of Postman running tests simultaneously. If necessary, I can open two Postman instances and compare them with another test. 

We also used LoadRunner to do some testing but that is for entirely different purposes. It's a load-testing tool for performance, whereas Postman is used more for functional testing. We mainly use Postman mainly to when a thing has occurred in your form. So when we're doing integration testing and all that, we use Postman. It is almost like a manual test where the processes are entirely different. For other purposes, we use tools like LoadRunner, Jenkins, and JMeter. We also use Selenium for automation testing and to execute our CFPB pipeline division. 

Setting up Postman is pretty simple. You just download it and run the installer. It only takes one person to install and you can do it in around 10 minutes.

I rate Postman eight out of 10. I recommend investing in Postman, which has a lot of features. You can use it to save scenarios then export, store, and reuse them. Postman already has a lot of features that I like.

We're a big organization. I'm not sure how many employees we have, but everyone on our team uses Postman. We use Postman mostly to do API testing for a U.S.-based telecom company. I work in a middleware layer, so we get a lot of events from some other subsystems. Events are sent to a particular pipeline comprising Rabbit MQ and Kafka. It's not possible for our organization to simulate the events, like in a QA environment. It's not easy to create those events because they are sent by other companies or other systems.

Using Postman, we simulate these events by sending the events to that particular pipeline. Then we have a consumer application attached to that pipeline. When this particular event is triggered, it's captured and sent to Kafka, so we get a response in a system. It's basically a simulation. Some people try this in our organization itself. For my part, it's more on the DB side. 

Before integrating Postman, we were triggering events manually. With Postman you can do automation. Automation has increased efficiency by more than 30% or 40%. Because the speed has increased, it's also possible for us to do in-sprint automation testing. When we do manual test cases, we can add an automated test case in the same script. This makes it easy for us to do in-sprint automation. The client is also happy because each time they ask for something, we can provide that.

The most valuable aspect of Postman is its ease of use. If a new client comes to our organization, it is very easy to ask him or her to install Postman, then get the URL, and then provide them with the fields for mandate refills or whatever field is applicable. We can ask them to get the JSON. We can even create validations and assertions. Postman can also be integrated with another tool called Newman. 

Postman also has strong reporting features that allow us to create reports and then send these to the stakeholders. We use regularly scheduled reports. Every day at 10:00 a.m. our time, a report will be generated and sent to the stakeholders. We do a regression daily, and everybody gets the report also. It's a very user-friendly tool. Anybody can learn it. In my case, what I do is create an input Excel sheet when I give all the values. It takes the values from the Excel sheet. In the pipeline, we have something called YAML script Baron.

The automation tool requires a little work. You have to spend some time initially, but after that, you don't have to worry about it. For a given set of test cases, I create automated test cases and then add them to this particular regression suite, so that everything will run. If somebody asks me to run a regression tool, I can easily show them the results. It's all in the report, and they can click on it to see the input value that I've given. 

To get this email reporting function, we have to integrate Postman with Newman. If the two are not integrated, we won't be getting all these things in one group. I'm not sure if the open-source version of Postman has that. I need to check. If it doesn't, then that's something Postman could add as a native feature.

I've been using Postman for three years.

Postman has never failed. Maybe once or twice depending on my internet connection. But generally, no issues from the Postman site.

We have integrated Postman with Newman, and that is working fine.

I've never had to call Postman support actually. If you want to integrate something, you can turn to community forums and online sources. When we were trying to integrate Postman and Newman, we could just Google it. We didn't have to call anyone. 

We've used other solutions in parallel with Postman, like ADAPT Test. ADAPT is more of a service virtualization tool, but we can also do API testing in that particular tool. We were finding it difficult because it taking time for us to open the tool. Frequently, we were getting some error messages. On the other hand, we had support. It's a good tool, but it was not that stable. Eventually, we decided that we would just stick with Postman.

Postman setup was straightforward. It was not complex

It's open-source, so I don't think a cost is involved.

If you're getting started with API testing, Postman is the first tool I would suggest for anybody who wants to learn API. It's easy. Later on, you can try SoapUI and finally move on to ADAPT Test. It's easy to teach and train others to use Postman. I can share my screen and tell them. It's not like I have to sit with them, then show them. There's nothing like that. It's very easy. Even a recommendation will do. When I'm teaching a person, I don't have to sit with them and tell them, "Click there. Click that." I can create a document and share it with them and they can do it on their own. 

I would rate Postman eight out of 10. I need to check on the email functionality though. If email is provided, I might rate it 10. I'm not sure.