Postman Enterprise Reviews

When critical things happen, and we need immediate testing, we use Postman or SoapUI.  For example, when testing ServiceNow applications, we use Postman to call the APIs. The data sequence of the APIs has to be called, so we create test cases in Postman that call the appropriate data, authentication keys, and everything else we include in the data. And when we post about it, we include all that data. We fill in all of the required fields and send the request. When we get the response, it will include some data. We capture that and send it along on the subsequent request. So we usually use Postman to keep our directors informed during our integration and product testing. It's a pretty mature solution. Postman is about seven to eight years old. 

Postman has helped up with storing data, sharing test cases, and reporting. It's much easier to share test cases with teammates. I don't have to deliver an Excel sheet with all the test cases in there. It covers my list of requirements. For instance, it gives me the raw data, and if I need a new structure or format, it does everything automatically. Back in 2012, it was a browser-based application that you open in Chrome, but now it's a desktop application. It makes my life much easier. The browser-based app was frustrating because Chrome uses a lot of memory, and the browser often crashed. 

Postman allows you to incorporate and export the test cases we create. It enables me to share the test cases with my colleagues, so I don't have to copy them into an Excel sheet. Postman lets me export the dataset and share it with my team. They can use my test case for their testing. 

It lists all the tests I have done, so I don't have to report them separately. With SoapUI, I can't do that. So every time I run a test case in SoapUI, I have to note in an Excel sheet the data, response times, etc. Postman sets the data free. It records the calls, responses, and everything else I need. So I can create a report and then go back and see what testing happened in the past month. 

Testing API is pretty straightforward in Postman, but it falls short when testing web services. For example, when we test web services, there is a visual component that we can import in SoapUI but not in Postman. It's pretty challenging to work with visuals in Postman, but it's much easier in SoapUI. We used Postman to test web services three years ago, but we found it wasn't suitable, so we started using SoapUI. If Postman's web services testing were smarter, it would be the number one tool we use.

It would be great if Postman could add some more integration with the other testing tools we use. For example, it would be nice if we could create a test case scenario in Postman and execute it using Jenkins during the CFPB pipeline. That would be an outstanding feature that we could use. Writing a lot of code for test cases in Selenium is much more complicated than creating a small test in Postman. So that'll make our life much easier.

I've been working with Postman for the past six years.

Postman is pretty stable. When I was using the browser-based version, it took a while to load. Now it takes a little time but not very much. It's about as fast as any other application. But when I was using the web app in my Chrome browser, the browser would crash, and sometimes my system would freeze. So we had that issue earlier, but the performance has improved a lot.

Postman is scalable. I can have multiple instances of Postman running tests simultaneously. If necessary, I can open two Postman instances and compare them with another test. 

We also used LoadRunner to do some testing but that is for entirely different purposes. It's a load-testing tool for performance, whereas Postman is used more for functional testing. We mainly use Postman mainly to when a thing has occurred in your form. So when we're doing integration testing and all that, we use Postman. It is almost like a manual test where the processes are entirely different. For other purposes, we use tools like LoadRunner, Jenkins, and JMeter. We also use Selenium for automation testing and to execute our CFPB pipeline division. 

Setting up Postman is pretty simple. You just download it and run the installer. It only takes one person to install and you can do it in around 10 minutes.

I rate Postman eight out of 10. I recommend investing in Postman, which has a lot of features. You can use it to save scenarios then export, store, and reuse them. Postman already has a lot of features that I like.

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.

We mostly use a REST API for testing related to third-party applications, integrating services with third parties responsible for food delivery. Use cases include onboarding for when a new store opens, uploading the menu on the third-party app. and an API for customers to order from a menu. We also use Postman for payments, whether debit or credit card. It covers all the validation points, including whether a card is fake, stolen, invalid or blocked. We are customers of Postman and I'm a senior consultant. 

We observed that in contrast to SoapUI Pro where you're only able to save your project, Postman allows you to also save your responses so that if something isn't working you can go to your saved results and verify the responses.

The solution is simple to use and you can easily store your projects. We mainly use Postman for our manual validation, but you can also schedule the automated validation. It offers multiple scenarios for a single API that you can run whenever needed. It offers a validation kind of functionality and the execution report of scripts. How many passed and how many failed. There's no manual intervention required, you click on the run button and that's it. The dashboards are good and the solution is user-friendly. The solution gives you the capability to run your use cases without manual intervention. 

The solution is quite complex and not so easy to understand at first glance. Part of the problem is the UI which needs simplification. There are many features available but they need to structure things more so that they're not scattered on the screen which complicates things. Each time you run the solution, you have to manually provide a username and password because those details are not automatic. That's a pain point for us. It also lacks a feature that will integrate with your database. I think this is a drawback of most applications whether it's Postman or SoapUI Pro. If you want to automate something when you're using the huge APIs, everything needs to be automated using dynamic data and that takes additional time. 

I've been using this solution for six months. 

We're a large organization and I imagine there are around 1,000 people using this solution. For maintenance and upgrades, our organization has the repository to maintain all software. Though it's freeware, you cannot install it directly and we have a separate team responsible for maintaining all the software.

We use the Postman community if we have any problems. 

The initial setup is straightforward. You just have to install the application, there is no complexity in that. Deployment takes a few minutes and then you build up your URI and start using it. In total, it takes less than half an hour. 

We don't pay for any license, the solution is freeware. There are some additional features that we do need to purchase.

It's important to figure out your requirements and if you need something special, then you will have to compare the different applications and figure out which gives you better results. 

I rate the solution seven out of 10.  

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 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.

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.

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. 

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.