Postman Reviews

I'm using Postman for manual testing of REST APIs. There are some built-in collections done by some of my teammates, so I use those.

The solution is deployed on a public cloud.

I have used some parameterization from a global variable, so that was working fine for me. It's easy to see different versions of responses. There's also a possibility for automation.

We cannot do database connections from Postman directly, and we don't have a way to do that. If they could implement auto-validations and assertions from SoapUI, that would be a very good feature.

We don't have a provision to go and connect to the database from Postman. That's one drawback. If you want to automate in Postman, there is a major drawback. Being a tester, you always want to cross-verify your data with the database. If the database is not connected, then part of your testing becomes manual.

I have used this solution for about seven years.

It's stable. Sometimes it has gone off, and I have had to rebuild the collections again. I've had to switch the logins sometimes. It has crashed twice, and I lost my suites and had to build it again.

Initial setup is easy. Sometimes we get the proxy errors, but when we go to the settings and disable the proxy things, it's pretty simple. Comparatively, SoapUI is easier for me.

Maybe some people who don't have a licensed version of Postman or ReadyAPI might feel that it's easier to automate with Postman, but I'm not sure about that because I haven't done it.

I would rate this solution as four out of ten.

If you don't have SoapUI or if you don't know about SoapUI, then of course you can use it. If you want to explore Postman, it's a free tool.

Postman is an API regression suite, and we design different workflow center processes. We maintain the Postman tool and add JavaScript applications. Since it is not that robust, like ReadyAPI, we have to write many scripts to support it.

The UI is good. It's appealing and free, and everyone can use it.

Postman needs more advanced data-driven testing. We have to provide the data filter in runtime only. It's not like software, and we can add different data sources. That feature is not in Postman yet.

We have been using Postman for one year.

It is not that stable because the bigger the APIs, the higher the chance of crashes. Also, it takes up a lot of RAM and system memory, so it is not that reliable.

It is scalable, but it takes up a lot of resources. We have 40 users using Postman, mostly from the dev, automation and manual test teams. We use the solution weekly.

Postman has a support center, but they are not responsive. Many issues are still pending. I rate the technical support a six out of ten.

Neutral

You complete some setup processes for an application and have to provide the URL. It is not a complex setup. With a bit of understanding of API, it can be set up. I rate the setup an eight out of ten. There is a dedicated framework team for maintenance comprising about six people. Maintenance is required every three months.

Postman is open-source and free to use. I believe there is a corporate license they add to make it more robust and fast, but everyone mostly uses the free version.

I rate this solution a seven out of ten. You can use Postman if you are a beginner or trying to learn API. Small-scale organizations can also use it because it does not need any license.

Postman is gaining pace because it supports the Google Chrome compatibility rate and plugin support. It is easy to set it up for the testing team. It is a good tool, but it still needs improvement for a scalable API tool.

Regarding advice, there are some secure APIs in different organizations, so it's better to get approval from your manager or architect so that APIs are not exposed. Also, it is important to be cautious about the organization's sensitive data before implementing Postman.

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.

We use the solution for API testing purposes.

The solution has helped us very well in testing endpoint URLs.

The solution's most valuable features are straightforward UI and the ability to identify specific errors.

They should integrate the solution with Salesforce.

We have been using the solution for one and a half years.

It is a stable solution.

The solution is scalable for testing purposes. We plan to increase its usage further.

The solution's initial setup process is pretty simple.

The solution has generated ROI for our organization.

The solution has all the essential features. I recommend it to others and rate it as a ten.

I use Postman for API testing. I use this solution for UI or automation purposes.

I like that it is very easy to use. I also like the automation feature.

It would be better if we could integrate programming languages like .NET, Java, and JavaScript. It could also be more user-friendly.

I have been using Postman for three to four months.

Postman is a stable product.

Postman is a scalable product. We have two or three users using Postman in our organization.

The initial setup is straightforward because we are IT professionals. 

On a scale from one to five, I would give the initial setup a 5.

I am using the free option.

ReadyAPI is very good, but you have to pay for it. Postman has a free option, and that is why I am using it. ReadyAPI is more user-friendly. For example, its features elaborate on what happened. You can right-click on the thing and add the features. In Postman, we have to find things from the inside and then get it into the project. The main difference with Postman is the ability to connect with different application tools integrated with Jira and database connectivity. 

On a scale from one to ten, I would give Postman a nine.

The main reason we are using Postman is for checking and validating the API whether it works fine or not. When they send a request, we will receive the response with a successful code or we will be monitoring the code number for the latest number record.

I have been using Postman for six to eight months.

One of the most valuable aspects of Postman is scalability. We can scale the collection and for the multiple repositories of the collections.

We have not used technical support from Postman.

I have used Apache JMeter previously.

The initial setup of Postman is easy.

We do the implementation of Postman and give support. We had to use two engineers for the implementation, one senior and one junior for the process.

I rate Postman a ten out of ten.

I use the tool to test the APIs that are developed. 

The developers put the API in a common workspace which is a nice feature. It makes things much easier and faster to start testing. 

I would like to see more integrations with other platforms. 

I have been working with the product for five years. 

The product is stable. 

My company has 100 users for the product. 

The tool's setup is straightforward and took less than an hour to complete. 

I would rate the product an eight out of ten. The product's user interface is better than others. 

We are using Postman to verify and test APIs.

The solution has helped us make better APIs. The solution is able to provide us with error reports if there are problems with the APIs. This has saved our developers time.

The most valuable feature of Postman is the verification and testing of APIs. 

Postman could improve the saving date capabilities. 

I have been using Postman for approximately five years.

The stability of Postman is good.

The solution is scalable.

All the developers in my company are using this solution.

I rate the support for Postman a four out of five.

Positive

I have used Swagger. I would recommend Swagger for the backend developers. The APIs only need to be set up once, then Swagger generates the document for all of them. In Postman the APIs need to be set up manually.

The initial setup of Postman is straightforward.

I rate the price of Postman a four out of five.

We evaluated other options before we choose Postman.

I rate Postman a nine out of ten.