Postman Reviews

We use this solution for manual API testing, which we call penetration testing. Postman provides a user friendly interface that can be used by non-technical team members. 

It is easy and simple to use and install. It is compatible with Linux, Mac or Windows. Postman is a great solution and resource for those who are new to technical platforms in terms of API development and testing. Postman is an open source solution and so is an affordable resource for those wanting to learn. 

I would like to have a code snippet where I can write a code and for the responses of the endpoints to be validated using my custom business conditions. In certain scenarios, we want to have custom business scenarios and not generic ones. 

We would like to have a code interpreter in Postman and also for automation to be less complex. My team want various complex automations using APIs depending upon their complex business conditions but automation using Postman is limited.

The UI of Postman could be enhanced by adding a proper panel or code. 

I have been using this solution for five years. 

This is a stable solution but user rights can be complicated and cause disruptions. 

This is a scalable solution but scaling it can be complex. 

For support, we use the open communities and documentation provided.

The initial setup is very straightforward.

This is an open source solution.

I have previously worked in the airline industry and used ReadyAPI. This is a licensed product and was used to ensure GDPR requirements and data privacy policy requirements were met. This solution costs approximately 800 Euros. Postman, on the other hand, is free as it is an open source solution. 

Running test cases using Postman is not as easy as with ReadyAPI. 

I would rate this solution a seven out of ten.

The primary use case for the solution is to test the response accuracy of services that we hit without the UI.

The most valuable feature is that JavaScript can be included as tests. That makes it easier to build an end-to-end API suite and it can be automated.

Integration of the solution towards Bitbucket, BitHub, and CI pipelines is difficult.

I have been using the solution for two years.

The solution is stable.

If used as a stand-alone solution it is easily scalable.

The initial setup is straightforward. You only need to download the solution from the internet and run it. The most complex part of the setup is setting up a proxy if it is required.

I implemented the solution in-house.

Unlike APIs, the solution does not require a license.

I rate the solution seven out of ten.

As a standalone option, it's a fantastic tool, but it's very hard for us to collaborate using the solution.

Our development people use the solution for testing.

The solution is a good tool to try out new APIs that the team is building or any existing APIs. It is relatively easier to build out scripts and automate certain flows. The solution as a standalone tool is beneficial in creating utility scripts. 

I use Postman as a testing tool. I used Postman for one of the education-based applications named Compass. I can use Postman effectively.

The most valuable features of the solution are that it is easy to use and user-friendly. I can use Postman with simple Java codes, along with some secret codes. With Postman, I can create some complex test suites. With Postman, I can get some statistical reports, making its use so much fun for me.

From an improvement perspective, Postman can help users create a stronger feedback loop along with quicker and more responsive support resources.

I live in Turkey, so for me, the value of dollar currency is high. Postman can change its pricing policy and decrease the prices for Turkey.

I have been using Postman for half a year.

Stability-wise, I rate the solution a seven out of ten.

Scalability-wise, I rate the solution an eight out of ten.

I worked with Postman all by myself in my IT group, but there is another group in my company with three or four members who use Postman presently.

I may use Postman even more for another project if needed in the future.

I rate the technical support a six out of ten.

Neutral

I use Selenium as a web development tool and testing tool. I also use Azure Database for MySQL.

I rate the product's initial setup phase a ten on a scale of one to ten, where one is a difficult setup phase, and ten is a very easy setup.

The product's installation phase is very easy.

The solution is not deployed on a cloud model.

The solution can be deployed in six or seven weeks.

The product's deployment process revolves around controlling back-end activities while also keeping control over the part of writing output codes, after which I could classify some tests on it. The deployment process of the product was easy.

I was alone in the project for deployment, as it was not so complicated for one person.

I could take care of the deployment of the product by myself without any other person or support.

I rate the product's price a nine or ten on a scale of one to ten, where one is cheap, and ten is very expensive. Postman is an expensive tool for Turkey.

I researched other applications in the market and found that Postman is better than the others.

I can recommend Postman to others.

Considering the shortcomings that stem from Postman's pricing model and issues with support, I rate the overall tool an eight out of ten.

Our developers use the product for unit testing and integration testing. Our QA team uses it for functional testing where we measure the performance of the scripts written in Javascript. We also rely on JMeter so that we don’t need to spend double the time on rewriting those tests again.

For example, contract testing will have scenarios that will contain around 20 API calls. After the login, you can create the data, edit or delete it, verify the changes, and log out. This will be one test case. There will be around 20-30 test cases. The script file will contain around 30 test cases written in a row.

Postman helps to write pre-request scripts and make a collection out of each request. You don’t have to spend time writing or copying the requests. The solution lets you integrate multiple environments and their features. Either the tool’s pro or premium version lets you do the merge and pull request for the Git directly.

Azure was really painful. Azure detected and exported collection files that were different every time. If your request had a unique ID, then it was really painful. The integration with Postman was really helpful. You will be able to see normal one-line changes. When we integrated Swagger definitions in Postman, the developers were able to see changes and differences when they update API descriptions.

I would like to see improvements in the maintenance of the scripts and their collections. It is really painful that the user cannot drag and drop. It was also painful to create the standard suite of operations for the product. I am not sure if this is improved in the tool’s latest versions. The maintenance of the complex scenarios prompted us to use the solution only for unit testing. In the future, we may switch to the k6 framework.

I have heard that solution is trying to implement the extension for VS Code. I am not sure about this since I haven’t used the latest version. However, I tried the latest version for an interview. The new UI confused me.

I have been using the solution for a year.

I would rate the solution a seven out of ten.

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 Postman from time to time to test real-time API connections.

When I receive documentation regarding API services, I use Postman to verify that the explanation in the documentation I received is working as described. In general, the tool is good for testing purposes.

The most valuable features of the solution are drafting requests, pushing the standard, and receiving responses. The tool's basic operational stuff is valuable.

The automation testing capability is something that I haven't used. In the past, I have used SoapUI to automate tasks, but I haven't tried it in Postman. I was not even aware that it was possible to automate tasks in Postman.

Some features related to the automation of tasks need to be added to the solution. The tool may already have some automated testing features, but I haven't discovered Postman's full operational status. When I need the tool's automated testing features, I will certainly have a look at the documentation.

I have been using Postman for four years. I am a user of the tool.

Stability-wise, I rate the solution a nine out of ten.

The stability of the product has been better since last month.

I have experience with SoapUI. The environment where I work for the moment is more Postman-oriented. In the past, some government departments in Belgium were using SoapUI. Postman is similar to SoapUI. The features in SoapUI, for instance, the automated testing features, are things that I don't need at the moment. Postman performs how I like it.

The product is easy to implement. You need some knowledge to implement the product. As I was more or less familiar with SoapUI, I could very easily pick up the way Postman works.

I use the tool's free version.

The product is not used for collaboration but for testing purposes in my company. In short, I use the product, and it is not used for exchanging or exporting data. I use the product at a very personal level, considering its API-related capabilities.

The tool performs well enough to meet my expectations.

I rate the tool an eight to nine out of ten.

We use Postman for testing and documenting APIs. I'm the technical director. 

Postman helps me recreate our client environment so I can send different parameters and get that authentication information. Postman helps me simulate the API code from a fictitious client application so that I can check the API behavior. It gives you a good ecosystem, especially when you have a multi-discipline team that is scattered. It's a great product, easy to use, and people like it. 

I think they could make version management easier and release it when it comes to container-based or Docker-based architecture. The solution is not really integrated in the sense that there's no distinction regarding single-tenant or multi-tenant use, or whether there are different versions for different container applications. Different versions of APIs might be required but there's currently no distinction between them. 

I think Postman should now focus on integrating into the whole DevOps and CI/CD pipeline and publish more white papers and articles to make it easier for somebody doing the DevOps and integrating Postman into the different development scenarios. 

I've been using this solution for five months. 

The solution is very stable. We were able to test it and simulate different client experiences. 

The solution is scalable, we use it for millions of customers' API codes. 

We haven't needed to contact technical support because the documentation is very straightforward and very helpful. It has good community support.

The initial setup was straightforward and was carried out in-house.

We've been using the open-source version until now, but I think within the next six months we might move to the enterprise solution. Licensing costs are reasonable, in the mid-range. There are more expensive solutions. 

Postman has taken the development community by storm. A lot of developers are using Postman for different things. Not everybody understands the end-to-end capability of Postman yet; one person might think it's only for testing, another that you can build applications, and somebody else might use it for documentation. Different developers look at it from different perspectives, and it has huge versatility. 

I rate this solution nine out of 10. 

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.