Postman Reviews

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.

We use Postman for testing the functionality of REST APIs. 

Within my organization, there were roughly five people using this solution, however, currently, I am the only person who is developing API testing tools.

The user-interface is very good.

Actually, I received some errors regarding the testing of SOAP APIs. There's definitely some space for improving the user's experience. There needs to be more flexibility surrounding the testing of SOAP APIs. Currently, they are primarily based on JSON files — invest APIs actually.

I know that SOAP APIs are considered a little outdated but they're still in use. Unfortunately, because of this, I have to search for another solution that supports SOAP APIs, because Postman doesn't.

I have been using this solution for roughly one year.

It's a very stable solution. Regarding the overall stability of the application and the test results that achieved — It's really a good application.

We haven't really had to contact technical support. We have been able to solve nearly all issues via online forums.

It's not exactly complex, but I wouldn't say it's straightforward either.

The deployment process was very quick; I believe it took roughly one week to get it all set up. Still, not all test cases were set up within that time period. 

All implementation was done by our in-house team.

As we only had 10 APIs to test, we used the free version.

Recently, I compared Postman with JMeter 12 for testing the load performance of the same APIs.

I would absolutely recommend this solution. It's one of the best solutions for testing REST APIs.

I had some great experiences using Postman, especially relating to REST APIs. Currently, I am in the process of learning about other tools suitable for API testing regarding SOAP APIs.

On a scale from one to ten, I would give Postman a rating of eight.

We are using Postman for our testing and checking our API response and validations.

What is most valuable for me is that we can create and share collections between the team members.

An area that needs some improvement would be to allow multiple windows with different collections to be open at the same time. 

It only allows you to open one with the same collection. 

If we open a new Postman window, it does not allow me to have the same collection as I had in the previous window. Allowing us to have replicas of the same collection open independently would be helpful.

I would like to see if it can incorporate Jenkins integrations.

I have been using Postman for five years.

It's a stable solution. It's running well.

Scalability is not for load testing. 

You cannot scale vertically. You can only scale horizontally.

I haven't contacted technical support, but they do have good documentation available online.

We are using the free version that is available.

It's a good tool overall and quite stable.

It is mainly used for testing purposes, API responses, and validations.

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

Our primary use case for Postman is API testing for our product. We haven't automated the request and response part yet, like how we used to do for automation scripts. Basically, we are just shooting the URL's and recording the response. As of now we have multiple API's and we are using the collection so that we can run it together in a single flow, like an automation execution.

Then we use the basic variables and the collection variables. We even saw that we have some additional validation through the response code and the status code, like if there is an expired date then we should be expecting 200 status codes. We are doing those kinds of things now. We have been using Postman for the API testing for two to three month.

The variables part is good. We can easily define the variables and we don't have to manually do a change every time, it gets automatically updated. Secondly, I like the validation feature which is required for our automation testing. This way we can see that our test case passed. I think we could add some more validation but we need to do more research on that. For example, how can we play with it and find the response code and the other statuses? We need to do more research on how we can validate the exact response and the code, and how we get the response messages.

We prefer Postman as it is the most usable solution. It's really accessible. We also use SoapUI for API testing. But we prefer Postman, based on the reviews, based on our research, and how easily the solutions are available if we get stuck somewhere.

In terms of what can be improved, I would expect extra features that would make our work easier.

I just saw that it's functioning is based on the machine. Meaning, if we have a certain build on one machine it won't work with another build even if we are using the same URL. It would give us a connection refuse. So developing environment compatibility would make it better. 

Other than that, I don't see anything more to improve. As it is now, I get for a return whatever I am expecting. That's why I gave it a seven or an eight. Because I'm not expecting much on that portion.

Because, we are mostly focused on that I would expect more validation points.

In terms of stability, it didn't crash or take time to load or anything like that. We did not face any issues with stability. It's a very old tool, so it's been used a lot. It gets daily usage.

Right now, two to three people are testing it and other people are joining in. We have individually different user ID's and we don't have to go chasing anything because we are using the free version now. Because we are not using the paid version I won't be able to see the scalability yet because we are just doing the basic stuff, such as a request hit and run.

The initial setup is very straightforward. We just have to download and do the setup. We already have the collection so we just have to share it with the teams and import the project. Furthermore, we didn't create the project and we had to do everything manually before creating the variables and still the installation was not complex.

We also use SoapUI.

On a scale of one to ten I would rate it an eight.

My primary use case is for API testing. 

The interface and the different types of API methods you can use are the most valuable aspects of this solution.

The pricing should be adjusted for the Pro plan.

I have been using Postman for over a year. 

It is quite stable. I don't use it quite extensively but for what I use it for it's quite stable.

At my current company there are around 2,000 users. 

I haven't used technical support. The documentation is quite good. I use the Postman website and forums. 

The deployment depends on what you are going to use it for. It can be simple and it can be complex at the same time.

When it comes to anything API related, I would recommend this solution. For anything API-related, it's perfect. REST API is the way to go and I would recommend Postman for it. 

I would rate it an eight out of ten.

The pricing is the only improvement. Its competitors are quite pricey. But it would be nice if there were more options like annual, monthly or enterprise-level.

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. 

The most valuable feature of this solution is Collections. It perfectly suits a microservice factor.

The workspace is very useful. You can save configurations in their cloud so that you can access them from home, or at the office because you log in to the same account. You don't have to recreate them.

I have display issues in my Windows that need to be fixed.

This is a stable solution. It's perfect.

We have between fifty and sixty employees who are all using this solution. We do not have plans to increase usage at this time.

I have not yet needed technical support for this solution.

We did not use another solution prior to this one.

The initial setup of this solution is simple and pretty much straightforward.

I can just open up a tab and use it.

We have perhaps ten people who maintain this solution

We are currently using the free version, but we have plans to buy a license.

I tried another solution but it was incompatible.

I'm perfectly happy with this solution and I'm really enjoying it.

I would rate this solution a nine out of ten.