Postman Reviews

I use it to check web services. For instance, I can send a request and receive a response. My company, which is in the insurance industry, uses it as well.

It is very easy for me to use and I highly prefer it compared to SoapUI and other products for performing its job. It is more handy and faster. It has impacted us very nicely. 

Postman is used for free by us. I'm not sure if there might be a paid version for multiple users. It is a very good product used for development. It is easy to install, as well as to learn, particularly for new users, even if they are not developers. I taught my business analyst to use it. I just showed them once, and it was easy for them to understand. 

For example, I gave them the URL and request format and asked them to test independently. They were able to use it on their own and do their testing as well. It was a good experience, especially for generally smart people, like those we usually hire in our company. It is pretty easy to explain, and learning it is not complex.

The primary use case for Postman is mostly for unit testing of the APIs. Additionally, I have developed scripts for end-to-end testing of the APIs.

One of the biggest advantages of Postman is its user-base approach. All collections created in Postman are not maintained locally and are instead maintained on the server, making it easy for me to continue work from anywhere if I log in with the same credentials. Any team member can continue the work as nothing is maintained locally.

I have not yet used Selenium within the last 12 months; I just completed some POCs, but not actually used it.

There are many other tools that we are working on aside from Selenium.

We use TestIM, Katalon, and those are all UI function tools, and in terms of API, we are working on Postman and Ready API.

Personally, I have been using Postman for seven or eight years plus.

Postman is the easiest tool I know, there's no challenge at all. In fact, most of the Postman testing that we do is all locally, but when I say deployment, that deployment is for cloud, and whenever we want to run it in CI/CD, it's all on Azure and AWS, so it's one of the easiest things.

Postman doesn't require much time to deploy, just a few minutes or so. This applies to almost all the tools that we're working on; Selenium is one of the most mature automation framework tools we have, so there's no issue with that.

I don't find anything difficult based on my experience, but the organization of collection, running, and assertions in the last few years have been really good for me; the environment is managed well.

Postman is one of the easiest tools; I have not seen anybody complaining because it's just one Google search away.

It's easy to navigate because tons of documentation and examples are available.

It has helped significantly since it is easy; the development team and QA team all use it, enabling us to automate almost 70% of our APIs using Postman.

I am currently using Postman when working with different web applications. I use it particularly when working on APIs and endpoints, especially in testing REST APIs that I've built with Django REST framework in Python.

Using Postman has allowed me to efficiently conduct many tests on REST APIs. It has facilitated my ability to manage different data, handle various protocols, and process numerous customer requirements across various projects.

In our development, I basically use Postman just to test the APIs.

With the help of Postman, I explore API training and other features. It is beneficial to have flexibility, especially with API chaining. This feature allows me to combine and, with the help of some code, run multiple APIs at once. API chaining is a very good concept and easy to implement.

There is a regular set of use cases, such as basic logins and long-form fills and submissions. There is a regular data set that we pick from the APIs, mostly with the GET, POST, and PUT calls. These are the three API methods we use regularly.

We are using the local version of Postman that we download for manual testing of the API. We do the automation directly in REST Assured with Java.

It makes manual testing very flexible, It's very user-friendly. When we do it through the Swagger file, we just go directly through a URL and hit the request/response, and validate that. Postman is very easy to use even for a person who doesn't have much knowledge or technical skills. It's very easy to use Postman and validate whatever we want to do. It's very comfortable and doesn't really require a user manual. It's a very user-friendly tool, and in a corporate environment, anyone can use the tool very easily. That's a benefit of Postman.

I am working for an insurance firm, a big client in the USA. They wanted to upgrade the current technology with something new. However, they have legacy applications, and they don't want to handle APIs. They didn't want anything to hit their existing API since they have two layers of APIs. 

At the same time, there are different components with around 17 to 18 integrations and various applications.

We wanted one tool that could help us handle the restrictions and the implementation. This is both an API and a very helpful testing tool. It's user-friendly for everyone using it in a big firm.

There is a product called Guidewire that sends the data in an XML format. It's like a policy load. That information we trigger in Kafka. Kafka will take the information and send it to the REST API. With Kafka, they wanted to make two APIs to consolidate the effort. At that time, we are using the POST API tool. This tool is helping us to synchronize everything.

I use Postman to test REST APIs. I work with Node.js and create or modify multiple endpoints, and I use Postman to verify if the endpoints work. Additionally, I use Postman to test other endpoints, like public endpoints.

In Postman, we have collections that contain multiple endpoints that I can test. I can use multiple environments, which allows me to create environment variables for each endpoint.