Postman pros and cons

With Postman you can do automation. Automation has increased efficiency by more than 30% or 40%. Because the speed has increased, it's also possible for us to do in-sprint automation testing.

We use it for REST API testing. Feature-wise, it is pretty lightweight. It is pretty fast, and we don't have to do a lot of things. We can just simply go and post our endpoint, and it gives different kinds of authorizations. We usually use authentication 2.0, which is the most common industry practice. So, it has the support for authorization through 2.0.

Postman allows you to incorporate and export the test cases we create. It enables me to share the test cases with my colleagues, so I don't have to copy them into an Excel sheet. Postman lets me export the dataset and share it with my team. They can use my test case for their testing.

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.

Simple to use and you can easily store your projects.

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.

The user-interface is very good.

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

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

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

To get this email reporting function, we have to integrate Postman with Newman. If the two are not integrated, we won't be getting all these things in one group.

The request encryption could be one thing on which they can work a little bit. If we don't want to expose our production data but we still want to test our APIs on the production data, there should be a way to do that. It is not only with Postman. I think no tool in the market is doing that right now.

Testing API is pretty straightforward in Postman, but it falls short when testing web services. For example, when we test web services, there is a visual component that we can import in SoapUI but not in Postman.

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.

The solution is quite complex partly because the UI needs simplification.

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.

There needs to be more flexibility surrounding the testing of SOAP APIs.

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.

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

The pricing should be adjusted for the Pro plan.