Postman Reviews

The solution is used for testing APIs, building monitors, and scheduling everyday runs to check API health.

Environment variable setup, pre-request script, tests, and monitors are most helpful.

The initial setup is simple. 

The Postman monitor will give the pass and fail status in the console. It could serve better if there is a downloadable report which gives tabular details of response time against each API and a pass/fail count (graphical representation) after the monitor runs.

The performance needs to be improved. Postman application freezes when a whole lot of APIs run under a collection.

I have been using this solution for two years.

Observed performance issues when used excessively. The application freezes and needs a restart. The response of the app is slow while running a collection with a lot of APIs.

We do have some interaction with technical support. They are responsive and knowledgeable about the product.

Positive

I used SoapUI previously. I found Postman to be more interactive and accessible compared to SoapUI.

It's a very straightforward solution to install. I'd rate the process five out of five in terms of ease of deployment. 

I'd rate the solution eight out of ten.

We're a big organization. I'm not sure how many employees we have, but everyone on our team uses Postman. We use Postman mostly to do API testing for a U.S.-based telecom company. I work in a middleware layer, so we get a lot of events from some other subsystems. Events are sent to a particular pipeline comprising Rabbit MQ and Kafka. It's not possible for our organization to simulate the events, like in a QA environment. It's not easy to create those events because they are sent by other companies or other systems.

Using Postman, we simulate these events by sending the events to that particular pipeline. Then we have a consumer application attached to that pipeline. When this particular event is triggered, it's captured and sent to Kafka, so we get a response in a system. It's basically a simulation. Some people try this in our organization itself. For my part, it's more on the DB side. 

Before integrating Postman, we were triggering events manually. 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. When we do manual test cases, we can add an automated test case in the same script. This makes it easy for us to do in-sprint automation. The client is also happy because each time they ask for something, we can provide that.

The most valuable aspect of Postman is its ease of use. If a new client comes to our organization, it is very easy to ask him or her to install Postman, then get the URL, and then provide them with the fields for mandate refills or whatever field is applicable. We can ask them to get the JSON. We can even create validations and assertions. Postman can also be integrated with another tool called Newman. 

Postman also has strong reporting features that allow us to create reports and then send these to the stakeholders. We use regularly scheduled reports. Every day at 10:00 a.m. our time, a report will be generated and sent to the stakeholders. We do a regression daily, and everybody gets the report also. It's a very user-friendly tool. Anybody can learn it. In my case, what I do is create an input Excel sheet when I give all the values. It takes the values from the Excel sheet. In the pipeline, we have something called YAML script Baron.

The automation tool requires a little work. You have to spend some time initially, but after that, you don't have to worry about it. For a given set of test cases, I create automated test cases and then add them to this particular regression suite, so that everything will run. If somebody asks me to run a regression tool, I can easily show them the results. It's all in the report, and they can click on it to see the input value that I've given. 

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. I'm not sure if the open-source version of Postman has that. I need to check. If it doesn't, then that's something Postman could add as a native feature.

I've been using Postman for three years.

Postman has never failed. Maybe once or twice depending on my internet connection. But generally, no issues from the Postman site.

We have integrated Postman with Newman, and that is working fine.

I've never had to call Postman support actually. If you want to integrate something, you can turn to community forums and online sources. When we were trying to integrate Postman and Newman, we could just Google it. We didn't have to call anyone. 

We've used other solutions in parallel with Postman, like ADAPT Test. ADAPT is more of a service virtualization tool, but we can also do API testing in that particular tool. We were finding it difficult because it taking time for us to open the tool. Frequently, we were getting some error messages. On the other hand, we had support. It's a good tool, but it was not that stable. Eventually, we decided that we would just stick with Postman.

Postman setup was straightforward. It was not complex

It's open-source, so I don't think a cost is involved.

If you're getting started with API testing, Postman is the first tool I would suggest for anybody who wants to learn API. It's easy. Later on, you can try SoapUI and finally move on to ADAPT Test. It's easy to teach and train others to use Postman. I can share my screen and tell them. It's not like I have to sit with them, then show them. There's nothing like that. It's very easy. Even a recommendation will do. When I'm teaching a person, I don't have to sit with them and tell them, "Click there. Click that." I can create a document and share it with them and they can do it on their own. 

I would rate Postman eight out of 10. I need to check on the email functionality though. If email is provided, I might rate it 10. I'm not sure.

Our primary use case is for API testing and I focus on automation.

I have enjoyed using parameters and setting parameters while powering directly.

I would like to see advanced automation in reference to Postman.

I have been using Postman for the past four years.

Postman is a stable product.

The scalability of Postman is suitable for my needs.

There is technical support online but not as much as Selenium. Postman has documentation and not live support. The documentation is around seventy to eighty percent of where it needs to be for Postman.

I have used Swagger and SoapUI. SoapUI does not have API automation. Postman is better than SoapUI when it comes to usability.

The initial setup of Postman was straightforward.

Postman is an open-source or free-source product.

I would rate Postman a nine out of ten.

I use this solution in my personal capacity. I use this solution to manage APIs. 

The downside of using this solution is that you need to know JavaScript. 

If you have knowledge of JavaScript, the initial setup is easy and straightforward. If not, it may take some time to learn about JavaScript before starting the implementation. 

We implemented this solution in-house.

I have only used the free version of this solution.

I would rate this solution an eight out of ten. 

I am using Postman for API tests.

Postman is a very important tool for API testing and it has helped our company.

The most valuable feature of Postman is the large libraries.

Postman quality assurance could improve when doing tests.

I have been using Postman for approximately two years.

Postman is a stable solution.

We have approximately 10 people using Postman in my company.

We only used the information we found online for support. We did not use the support from Postman.

I have not used a similar solution to Postman.

The initial setup of Postman is of a middle level of difficulty, it is not difficult or easy. However, it depends on the skills of the person doing it, it is easy for me.

We do not pay any money for Postman.

I evaluated other options and I found that Postman is more complete than other solutions.

I rate Postman a nine out of ten.

We used Postman to test APIs before implementing them. We used the latest version of Postman, and it was deployed on a private cloud, AWS.

It is one of the important tools in API testing, and it helped out team develop mobile apps. First, it allowed us to understand the working and performance of the APIs so we could know how long it takes to give a response and analyze. Then, if there were any problems, we fixed them and implemented them in the code.

The best thing about Postman is it was very easy to use, and we could test APIs and get immediate results. In addition, we could share all our APIs with our other developers securely.

It is not that easy to use and should have a more improved easy-to-use interface.

It was stable, and there were no issues.

We didn't use any other solution before Postman. A senior developer suggested Postman.

It was straightforward to install. We just downloaded it and used it as a tool for testing our APIs. We had a back-end developer and two mobile developers utilizing this solution.

Its usage depends on how many APIs we have to test. So we had a complete collection of APIs that we tested, and once we tested, everything was ready.

There are no licensing costs, and we used it for free.

I rate this solution a six out of ten because no solution is perfect, and every software has missing features. Postman should consider adding more features in the future.

Regarding advice, don't mix up all the endpoints and organize your collections according to the use case. It will be very helpful for other developers to understand the use of the APIs.

We are using Postman for testing APIs. It is simple, easy to use and a good tool.

One thing which Postman needs to improve is the documentation. The documentation of Postman is not that great when compared to other tools. 

I have been using Postman for two to three years.

Postman is a stable solution.

The scalability of Postman is good.

I have not had any experience with technical support.

The initial setup of Postman is straightforward. Setup is easy and you install it on your PC just like any other application from the browser.

Postman is a good, easy-to-use, and simple tool. I give Postman a nine out of ten.

Our company uses the solution for API testing. We have forty users who are trained in-house for various projects. 

The solution collects scenarios and allows for testing SOAP API, REST API and API automation at the same time.  

The solution's integration is useful for Jenkins or other tools.

UI testing needs to be added to the solution. The solution does not compare UI testing and API testing or API testing and database testing. To check data, additional tools are required for the comparisons. 

I have been using the solution for three years. 

The solution is stable. 

The solution is scalable for API testing but requires additional tools for UI testing or database testing. 

The initial setup is not difficult and you can find everything on the internet. I rate setup an eight out of ten. 

The solution is open-source and free. 

I also use Katalon Studio and Selenium because they allow for UI, database, and API testing together. For API test automation, Katalon Studio or Selenium are better than Postman. 

For just API testing, Postman is easy to learn and use.

I rate the solution a five out of ten.