Postman Enterprise Reviews

Our primary use case for the solution is data-driven testing for API. We get data from the environment, and we have some APIs to get the data.

The API testing features are valuable.

The solution could be more user-friendly and improve its documentation.

We have been using the solution for approximately one year.

The solution is stable.

We have not tested the extent of its scalability yet. Currently, ten people are using the solution in our organization.

We previously did not use other solutions.

The initial setup was complex because we had limited first-time user experience. I rate the setup process a six out of ten.

I rate the solution an eight out of ten. I advise users considering this solution to watch Youtube videos to bridge the documentation gap.

I use this solution in my personal capacity. I use this solution to manage APIs. 

The downside of using this solution is that you need to know JavaScript. 

If you have knowledge of JavaScript, the initial setup is easy and straightforward. If not, it may take some time to learn about JavaScript before starting the implementation. 

We implemented this solution in-house.

I have only used the free version of this solution.

I would rate this solution an eight out of ten. 

Our company uses the solution as a developer platform for testing APIs. Our backend team develops APIs which are then pushed to the solution for QA testing and configuration. 

It is very easy to create and manage different environments for testing. We can plug in different URLs and variables to test in a local environment before going to production. 

The solution has a great user interface and collection of features. 

Multi-part requests should be handled in the octet-stream subtype which provides responses in chunks for files that can be downloaded and viewed. We had an issue with multi-part requests recently and had to fix it. 

I have been using the solution for four years. 

The solution is stable with no issues. We have never experienced a problem or crash. 

The solution is scalable. An improvement to the octet-stream will enhance scalability for testing APIs. 

I have not escalated questions to support. One time I experienced an issue switching URLs in our environment, but haven't experienced it since. The solution's developers and QA team are continuously improving the product. 

The setup was really easy and was accomplished by configuring our email. 

Different projects automatically sync to the solution upon login so we are able to import files and configure API setups for other team members. 

We implemented the solution in-house and there is no maintenance because continuous updates are provided. 

I use the solution and other team members use Swagger. 

The solution is a great tool for managing APIs and should be used by developers and QA teams. It performs important testing for understanding how APIs work or whether any bugs exist and can be used to set up product domains. 

I rate the solution an eight 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.