Postman Enterprise Reviews

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. 

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.

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.

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.

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.

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.

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.

We also use SoapUI.

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

My primary use case is for API testing. 

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

The pricing should be adjusted for the Pro plan.

I have been using Postman for over a year. 

It is quite stable. I don't use it quite extensively but for what I use it for it's quite stable.

At my current company there are around 2,000 users. 

I haven't used technical support. The documentation is quite good. I use the Postman website and forums. 

The deployment depends on what you are going to use it for. It can be simple and it can be complex at the same time.

When it comes to anything API related, I would recommend this solution. For anything API-related, it's perfect. REST API is the way to go and I would recommend Postman for it. 

I would rate it an eight out of ten.

The pricing is the only improvement. Its competitors are quite pricey. But it would be nice if there were more options like annual, monthly or enterprise-level.

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. 

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 Postman for API testing, and I am also using it for training purposes.

I have found that our time is significantly saved in terms of debugging and writing down the code manually as Postman allows us to add the code with the help of test and assertions, eliminating the need to write code ourselves.

The user interface is very easy to learn and use, and it is a lightweight application. It's also an open-source tool for API testing. One of the best features is that you really don't need to be an expert in any programming language because Postman can generate the codes automatically for you.

Postman needs to improve its support for a lot of integrations. Additionally, browser add-ins or extensions would be helpful.

I have been using Postman for quite a while, perhaps for the past seven or eight years.

The initial setup is very easy and simple.

Being an open-source tool, it's a lightweight tool that I would prioritize as number one.

I would prefer Postman as my priority since it's an open-source tool, simple to install and use. You don't need to be a programming expert to use it, which presents several advantages.

I'd rate the solution nine 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.