Postman Reviews

Our company uses the solution as a developer platform for testing APIs. Our backend team develops APIs which are then pushed to the solution for QA testing and configuration. 

It is very easy to create and manage different environments for testing. We can plug in different URLs and variables to test in a local environment before going to production. 

The solution has a great user interface and collection of features. 

Multi-part requests should be handled in the octet-stream subtype which provides responses in chunks for files that can be downloaded and viewed. We had an issue with multi-part requests recently and had to fix it. 

I have been using the solution for four years. 

The solution is stable with no issues. We have never experienced a problem or crash. 

The solution is scalable. An improvement to the octet-stream will enhance scalability for testing APIs. 

I have not escalated questions to support. One time I experienced an issue switching URLs in our environment, but haven't experienced it since. The solution's developers and QA team are continuously improving the product. 

The setup was really easy and was accomplished by configuring our email. 

Different projects automatically sync to the solution upon login so we are able to import files and configure API setups for other team members. 

We implemented the solution in-house and there is no maintenance because continuous updates are provided. 

I use the solution and other team members use Swagger. 

The solution is a great tool for managing APIs and should be used by developers and QA teams. It performs important testing for understanding how APIs work or whether any bugs exist and can be used to set up product domains. 

I rate the solution an eight out of ten. 

We use it for our APIs. We also use it for automated testing.

In general, we have more visibility about the APIs that we have and how they work. We also have more visibility about the documentation. A lot of users are now familiar with APIs because Postman has quite a user-friendly UI. There is an educational improvement.

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.

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.

I have been using this solution for about two years.

In general, it has been quite stable. I did not see any issues apart from the recent issue related to importing collections in JSON.

We have around 10 users of this solution. It is good for now. We don't have plans to increase its usage.

I did not have an opportunity to contact them.

Its price is moderate as compared to other competitors. The version that we are using is not open source, so it is not free.

Make sure that the tool that you choose will solve the problems that you have and meet your goals. I only have experience with Postman, so I can't recommend anything else.

I would rate Postman a nine out of ten.

Almost all the teams here depend on the APIs, which are built-in SOAP or JSON. We have multiple teams testing JSON and they use Postman. There are multiple applications teams that integrate their interfaces with APIs, and they use the Postman.

We used to test APIs with different kinds of data by keying in the data from Excel sheets and using it to test APIs in Postman. But now, our testing is more data-driven.

Among the valuable features are

• data-driven automation
• response validation
• testing of the performance of APIs.
  

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

When you get a response, for example, if you search the response and want to know how many numbers of fields, it displays 10 times. If a purchase has five to 10 cards in the response, instead of one of the fields being mandatory, it has to be part of each section of the cards. 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.

Half of my career has been on web service testing only, and we have used Postman for JSON testing. For SOAP, we use ReadyAPI.

We only use Postman for JSON testing, but we don't have any issue with it.

We have also had no issues with scalability.

We have not had to contact Postman's technical support.

The initial setup is straightforward. It takes a maximum of five to 10 minutes.

The deployment is done by the development team. We have a giant scrum we follow. Development does the deployment using XL Deploy. And right now they are not using Jenkins.

I would rate it a seven out of ten. 

Our primary use case for the solution is data-driven testing for API. We get data from the environment, and we have some APIs to get the data.

The API testing features are valuable.

The solution could be more user-friendly and improve its documentation.

We have been using the solution for approximately one year.

The solution is stable.

We have not tested the extent of its scalability yet. Currently, ten people are using the solution in our organization.

We previously did not use other solutions.

The initial setup was complex because we had limited first-time user experience. I rate the setup process a six out of ten.

I rate the solution an eight out of ten. I advise users considering this solution to watch Youtube videos to bridge the documentation gap.

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 are using it to test the API service for the GET and the POST. For this type of test, it is working properly for the APIs. It tests for the minimum usage of Postman. Also, if developers insist in collections, then we can share these collections as well.

1. We can test APIs. We know if they are functional or throwing any errors. 
2. We can use the code for performance testing.

• It is easy to use.
• It's free.
• It's user-friendly. Anybody can learn it within five to seven minutes. 
• We are using the automation and performance testing tools. 

We would like to create an entire suite where we can check the contents of the definition, like the server file. It should be able to check the records and compare them to the regression testing more on the automation side.

We cannot see transaction times in the product.

You can send it multiple tests at one time.

We have not used technical support yet.

The initial setup was very straightforward. It was easy to install, because it is a very lightweight application.

It is free.

I am searching for other options now.

We started using this solution because we have a requirement to do more integration testing and automated regression testing.

Most important criteria when selecting a vendor:

• Saves time.
• Creates automate processes.
• Easy to use.
• Easy to understand.
• Provides knowledge transfer.
• Less coding involved.
• Does not take up a lot of memory.
• Cost.

We use the solution for API testing. 

It helps me to test APIs independently. It also supports hosting. 

The tool needs to have a reporting feature. 

I am using the tool for three years. 

The tool's free version is scalable. My company has about 100 users for the tool.

I never contacted the support team. Instead, I resorted to online help. 

The product's setup is easy. 

This tool is open-source and free to download and use.

I would rate the tool an eight out of ten. The product's features are simple. You will figure out to use the solution on your own. The tool is not hard to setup. 

My primary use case is for responses. I'm a user and work as a programmer analyst. 

This is an easy solution to manage. 

The solution can be confusing for first-time users so it could be made a little more user friendly. It's just click and proceed but still confusing if you haven't used it before. 

I've been using this solution for three years. 

No problems with stability. 

The scalability is good. I've used it in a company where there were around 200 people. It's generally used by an IT team.

I would rate this solution an eight out of 10.