Postman Review

We can easily define the variables and it gets automatically updated


What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How was the initial setup?

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.

Which other solutions did I evaluate?

We also use SoapUI.

What other advice do I have?

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

Which deployment model are you using for this solution?

Public Cloud
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Postman reviews from users
...who compared it with SoapUI Pro
Add a Comment
Guest