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.

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.

We are using Postman to verify and test APIs.

The solution has helped us make better APIs. The solution is able to provide us with error reports if there are problems with the APIs. This has saved our developers time.

The most valuable feature of Postman is the verification and testing of APIs. 

Postman could improve the saving date capabilities. 

I have been using Postman for approximately five years.

The stability of Postman is good.

The solution is scalable.

All the developers in my company are using this solution.

I rate the support for Postman a four out of five.

Positive

I have used Swagger. I would recommend Swagger for the backend developers. The APIs only need to be set up once, then Swagger generates the document for all of them. In Postman the APIs need to be set up manually.

The initial setup of Postman is straightforward.

I rate the price of Postman a four out of five.

We evaluated other options before we choose Postman.

I rate Postman a nine out of ten.

I am using Postman for API tests.

Postman is a very important tool for API testing and it has helped our company.

The most valuable feature of Postman is the large libraries.

Postman quality assurance could improve when doing tests.

I have been using Postman for approximately two years.

Postman is a stable solution.

We have approximately 10 people using Postman in my company.

We only used the information we found online for support. We did not use the support from Postman.

I have not used a similar solution to Postman.

The initial setup of Postman is of a middle level of difficulty, it is not difficult or easy. However, it depends on the skills of the person doing it, it is easy for me.

We do not pay any money for Postman.

I evaluated other options and I found that Postman is more complete than other solutions.

I rate Postman a nine out of ten.

Our primary use case is for API testing and I focus on automation.

I have enjoyed using parameters and setting parameters while powering directly.

I would like to see advanced automation in reference to Postman.

I have been using Postman for the past four years.

Postman is a stable product.

The scalability of Postman is suitable for my needs.

There is technical support online but not as much as Selenium. Postman has documentation and not live support. The documentation is around seventy to eighty percent of where it needs to be for Postman.

I have used Swagger and SoapUI. SoapUI does not have API automation. Postman is better than SoapUI when it comes to usability.

The initial setup of Postman was straightforward.

Postman is an open-source or free-source product.

I would rate Postman a nine out of ten.

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.

Our company uses the solution for API testing. We have forty users who are trained in-house for various projects. 

The solution collects scenarios and allows for testing SOAP API, REST API and API automation at the same time.  

The solution's integration is useful for Jenkins or other tools.

UI testing needs to be added to the solution. The solution does not compare UI testing and API testing or API testing and database testing. To check data, additional tools are required for the comparisons. 

I have been using the solution for three years. 

The solution is stable. 

The solution is scalable for API testing but requires additional tools for UI testing or database testing. 

The initial setup is not difficult and you can find everything on the internet. I rate setup an eight out of ten. 

The solution is open-source and free. 

I also use Katalon Studio and Selenium because they allow for UI, database, and API testing together. For API test automation, Katalon Studio or Selenium are better than Postman. 

For just API testing, Postman is easy to learn and use.

I rate the solution a five out of ten. 

We are using Postman for testing APIs. It is simple, easy to use and a good tool.

One thing which Postman needs to improve is the documentation. The documentation of Postman is not that great when compared to other tools. 

I have been using Postman for two to three years.

Postman is a stable solution.

The scalability of Postman is good.

I have not had any experience with technical support.

The initial setup of Postman is straightforward. Setup is easy and you install it on your PC just like any other application from the browser.

Postman is a good, easy-to-use, and simple tool. I give Postman a nine out of ten.

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. 

The main reason we are using Postman is for checking and validating the API whether it works fine or not. When they send a request, we will receive the response with a successful code or we will be monitoring the code number for the latest number record.

I have been using Postman for six to eight months.

One of the most valuable aspects of Postman is scalability. We can scale the collection and for the multiple repositories of the collections.

We have not used technical support from Postman.

I have used Apache JMeter previously.

The initial setup of Postman is easy.

We do the implementation of Postman and give support. We had to use two engineers for the implementation, one senior and one junior for the process.

I rate Postman a ten 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.