Postman Reviews

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.

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.

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.

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.