Postman Reviews

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 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. 

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 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 use it for our APIs. We also use it for automated testing.

In general, we have more visibility about the APIs that we have and how they work. We also have more visibility about the documentation. A lot of users are now familiar with APIs because Postman has quite a user-friendly UI. There is an educational improvement.

It is nice to have different workspaces. You have your personal workspace, and then you have a team workspace. In general, I like its UI. It is quite cool.

I have recently noticed that, for some reason, I am not able to import collections in JSON. It is weird because I was able to do it before. 

When you create a new collection and documentation, in tests, you usually have to click Save. If you don't click Save, your collections don't sync with other devices, which is something I don't like. It is not clear for the users in a shared workspace, and I usually forget to click Save and end up losing all the collections that I created. I create a lot of routes, and clicking Save all the time isn't efficient. Instead of clicking Save all the time, there should be an option to save everything in one go.

I have been using this solution for about two years.

In general, it has been quite stable. I did not see any issues apart from the recent issue related to importing collections in JSON.

We have around 10 users of this solution. It is good for now. We don't have plans to increase its usage.

I did not have an opportunity to contact them.

Its price is moderate as compared to other competitors. The version that we are using is not open source, so it is not free.

Make sure that the tool that you choose will solve the problems that you have and meet your goals. I only have experience with Postman, so I can't recommend anything else.

I would rate Postman a nine out of ten.

My primary use case is for responses. I'm a user and work as a programmer analyst. 

This is an easy solution to manage. 

The solution can be confusing for first-time users so it could be made a little more user friendly. It's just click and proceed but still confusing if you haven't used it before. 

I've been using this solution for three years. 

No problems with stability. 

The scalability is good. I've used it in a company where there were around 200 people. It's generally used by an IT team.

I would rate this solution an eight out of 10. 

Almost all the teams here depend on the APIs, which are built-in SOAP or JSON. We have multiple teams testing JSON and they use Postman. There are multiple applications teams that integrate their interfaces with APIs, and they use the Postman.

We used to test APIs with different kinds of data by keying in the data from Excel sheets and using it to test APIs in Postman. But now, our testing is more data-driven.

Among the valuable features are

• data-driven automation
• response validation
• testing of the performance of APIs.
  

We can also submit requests multiple times and it allows us to capture the response each time by using utility scripts.

When you get a response, for example, if you search the response and want to know how many numbers of fields, it displays 10 times. If a purchase has five to 10 cards in the response, instead of one of the fields being mandatory, it has to be part of each section of the cards. I would like that if you click on one of the fields you should be able to see the entire row of fields, names, and values.

Half of my career has been on web service testing only, and we have used Postman for JSON testing. For SOAP, we use ReadyAPI.

We only use Postman for JSON testing, but we don't have any issue with it.

We have also had no issues with scalability.

We have not had to contact Postman's technical support.

The initial setup is straightforward. It takes a maximum of five to 10 minutes.

The deployment is done by the development team. We have a giant scrum we follow. Development does the deployment using XL Deploy. And right now they are not using Jenkins.

I would rate it a seven out of ten. 

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.