Postman Reviews

There is a regular set of use cases, such as basic logins and long-form fills and submissions. There is a regular data set that we pick from the APIs, mostly with the GET, POST, and PUT calls. These are the three API methods we use regularly.

We are using the local version of Postman that we download for manual testing of the API. We do the automation directly in REST Assured with Java.

It makes manual testing very flexible, It's very user-friendly. When we do it through the Swagger file, we just go directly through a URL and hit the request/response, and validate that. Postman is very easy to use even for a person who doesn't have much knowledge or technical skills. It's very easy to use Postman and validate whatever we want to do. It's very comfortable and doesn't really require a user manual. It's a very user-friendly tool, and in a corporate environment, anyone can use the tool very easily. That's a benefit of Postman.

In Postman, we have an option to directly import a call, make it a Postman collection, and execute it in a batch. This feature is very useful. It saves a lot of time. The manual effort is also reduced when we can just pick it in a Postman collection and then run and execute it to get the results.

When you try to code something and put it in the code, it's not useful. We have our developers or testers who know Java, but Postman is not flexible to use. The option to code in Java is not there in Postman. In ReadyAPI, we do it through Groovy scripts. If there was a provision in Postman to write down a few steps in Java code and run them together, that would be an improvement in Postman.

In Postman, for now, we are just doing API validations and running API scripts. If there is any way to have a record and playback feature through UI, as we do in Selenium and IDEs such as Eclipse, it would be great.

It has been almost two years.

It's very stable. I haven't faced any Postman crashes. Very often, you have latency issues. When there are any additional pop-ups or more tasks when it's open, there are a few latency issues. Other than that, it's a good tool.

Performance-wise, it's pretty good. On average, it does the job right. It's good enough for our requirements.

It's scalable. They have put a lot of new features into Postman. They have developed it in terms of UX/UI designing as well as features like runner, input level, and raw text level. So, it's scalable, but the downside is that they don't have any UI level of testing, and it cannot be integrated with any other supporting tool. It's not scalable in that way. 

I don't know the exact count, but we probably have 100 to 150 people using it. We use it very frequently. We use it on a daily basis.

So far, I haven't faced any challenges with it. I haven't been in touch with their support.

I also work with ReadyAPI. ReadyAPI is a more advanced tool than Postman because a lot of heavy data can be driven and a lot of test cases can be automated and triggered on a daily basis. That's how I worked with ReadyAPI. Postman is more of a manual effort tool, whereas ReadyAPI is more of an automation tool. It did have the option of scripting in Java or JavaScript, but I just worked with Google Script with ReadyAPI. So, I haven't worked on any other programming language with ReadyAPI, and I'm not very sure whether it supports any other languages such as Python or JavaScript. Other than that, it works very well for regression cycles. Getting the email-triggering functionality was also very good. If you want to have a lot of automation and run it on a regular basis, it's one of the recommended tools.

It's straightforward for me. I've been using Postman for a while. You can just directly download Postman from the web and use the version on your desktop. It takes minutes to download the EXE file and install that. It takes around 10 to 15 minutes.

Its updates are not very frequent. It's once every six months or one year. There are not many failures in Postman.

We are using its free version.

You can just give it a try. You can start with the free version and later upgrade to the paid ones. You would be able to do most of the things through the free version of Postman.

You can just learn the basic commands of Postman, various types of authentications, and the basics of API. You can learn how to send the environment variables, how to set the headers, etc. If you know all these things, it's very easy to use the Postman tool on a daily basis.

It's a very good product. I would rate it a nine out of ten.

We have been using Postman primarily for API automation.

API automation is crucial because every change in an API could have a significant impact. Postman has greatly reduced the effort required in testing APIs, thus enhancing our efficiency.

Postman is easy to use and enables us to test all possible API testing scenarios. It is economical compared to other testing tools, which is a valuable feature for us.

The main improvement needed is better integration with test management and other tools to allow a common dashboard for all testing metrics and details.

We have been using Postman for four to five years.

Postman is stable enough for our needs, although we have not tested it extensively with a large number of test cases.

We did not test Postman with thousands of test cases, so we cannot comment on its scalability for larger repositories.

We have not contacted Postman's technical support as we have managed all our needs internally.

Positive

Prior to using Postman, we used SoapUI. SoapUI was very basic and lacked many features that were then added in the paid version, SoapUI Pro, which was expensive. Postman provides better features than SoapUI.

Installation of Postman is straightforward and can be completed in a few hours by one person.

We did not require any external team for the implementation and managed it internally.

The return on investment is significant due to Postman's efficiency in automating API testing, which involves many input and output parameters.

Postman is economical and is considered to be rather cheap compared to other software solutions.

I have evaluated other tools such as Katalon, Tricentis Tosca, and Universal Function Test (UFT) from OpenText.

I would recommend enhancing Postman's integration capabilities with test management tools to better consolidate testing metrics.

I'd rate the solution eight out of ten.

I am working for an insurance firm, a big client in the USA. They wanted to upgrade the current technology with something new. However, they have legacy applications, and they don't want to handle APIs. They didn't want anything to hit their existing API since they have two layers of APIs. 

At the same time, there are different components with around 17 to 18 integrations and various applications.

We wanted one tool that could help us handle the restrictions and the implementation. This is both an API and a very helpful testing tool. It's user-friendly for everyone using it in a big firm.

There is a product called Guidewire that sends the data in an XML format. It's like a policy load. That information we trigger in Kafka. Kafka will take the information and send it to the REST API. With Kafka, they wanted to make two APIs to consolidate the effort. At that time, we are using the POST API tool. This tool is helping us to synchronize everything.

The version control is great. It can detect IP addresses really well.

It has a helpful API network.

The scalability is good.

It has been stable.

I haven't seen anything lacking in the solution. 

Support is not that good.

We'd like to see videos or user-friendly reference documentation to help us figure out the solution or troubleshoot issues on our own. That would be especially helpful for first-time users. 

I've worked with the solution for 18 months. 

The stability is okay. It's pretty reliable. I'd rate the stability seven out of ten overall. 

The scalability is good. I'd rate it eight out of ten. 

We have 70 top 80 people using the solution right now. 

We likely will increase usage in the future. 

Technical support hasn't been too helpful. On top of that, the documentation is lacking a bit. They're okay. They could be better.

We did not previously use a different solution. 

My understanding is that the solution is straightforward to set up. There are some challenges, sometimes, around configuration, specifically with REST API, however, it's not too difficult.

I'm not sure how many people are needed to deploy and maintain eh solution. We have a team of five or six, and we can handle it internally. 

We handled the setup in-house. We did not need outside assistance. 

I wasn't involved with the pricing. I'm not sure what the exact licensing costs are. My understanding is it is not too high. 

From a collaboration point of view, it's a useful tool. It's also super user-friendly. I'd rate it nine out of ten overall. 

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.

We used the solution in multiple ways, including:

1. We create Rest APIs for the communication of the front end to the backend. For the testing of those Rest APIs, we use Postman. It provides a user-friendly platform for API testing with all the request methods like GET, POST, PUT, DELETE, PATCH, and many more. We can create our own collections like group requests. We can easily share the collection with the team.

2. We are using Postman to create the documentation of the REST APIs, which the backend team creates, so the frontend engineer can easily see the request type, headers, methods, and response body for the request. 

3. It is also used as an API testing tool by the automation testing team. We can write our own tests with the assert statements in Postman after the response. 

Postman helps us to automate the API testing in the team.

It helps to share the Rest API documents with the front-end team so that they can easily integrate the API with the front-end.

It also helps in the monitoring of the APIs to check the health of an existing API.

It makes API development and testing faster and more user-friendly. It does not require any prior knowledge to work with the Postman. 

It supports the GQL requests as well as the REST API.

It allows all the request methods like GET, POST, PUT, PATCH, DELETE, COPY, OPTIONS, LINK, UNLINK, and many more. 

It allows all types of authentication requests like API Key, JWT bearer, Basic OAuth, OAuth 2.0, Bearer token, and many more. 

It allows us to set the environment variables as per our different environments, like QA1, QA2, STAGE, DEV, PERF, and UAT.

It allows you to write the pre-request script that runs prior to any API call. 

It allows us to save requests in a collection and share the collection with the team.

There is no support for the SOCKET testing with Postman.

There is no support for the testing of the SOAP APIs.  

Sometimes it crashes when a lot of collections are imported in a Postman.

There is no mechanism for parallel testing. 

There is no scope for load testing like in JMeter. 

There is low script reusability. 

It does not support SMTP protocols; it only allows HTTP protocol.

It does not allow for a data-driven approach. It cannot get the data from a database and use it for testing purposes.

I have been using Postman for the last three years.

It is easy to use and is a lightweight solution. For the last three years it has been working perfectly fine, and we are using it for API development, API testing, and documentation to share with the front end.

We can easily use Postman for large projects. We can create collections - as many as we want - and share them as JSON, for example.

There is a huge community of Postman users. I have never had a chance to connect directly with the support team of Postman as I get help online. 

Positive

We have been using Postman from the start as it is user-friendly and does not require any prerequisite language to use it.

It's quite easy to set up. You simply download it and then install it and start using it. 

We are using the free version as of now. However, the paid version allows users to create the workspace and share the common collection with more than four teammates.

We evaluated Katalon as well.

It is easy to use. However, it does not allow for Socket and SOAP API testing.

I use Postman for API testing and plan to start using it for automation testing.

Postman is useful for API testing. It also allows me to have multiple workspaces to share with my developers. I've just started using the mock servers and defining the flows, but that will take time.

The scalability of the solution can be improved.

I have been using Postman for more than seven to eight years.

The solution is stable. I rate Postman a ten out of ten for its stability.

The solution is scalable. Currently, three people are using the solution in my company. I rate Postman a six out of ten for its scalability.

I raised only two queries to the support team in the first month. I got responses for both of my queries when I was creating my mock service. So, the customer support was quick, and my issues were resolved.

The initial setup is easy and I rate Postman a ten out of ten for its initial setup. The deployment of the solution doesn't take much time. It just requires a few hours.

The solution has moderate pricing. We pay on a yearly basis for the solution’s licensing fee. I rate Postman a six out of ten for its pricing.

I have not yet updated to the 10.12 version of the solution. I use the solution very, very often, four times a week. I would recommend Postman to other users.

Overall, I rate Postman a nine out of ten. Once I cover the mock servers and automation, I should be able to give a higher rating.

We use the solution for rest API testing purposes.

The solution's most valuable feature is code-based API testing. The technicians have complete control over the business logic code in the test tool.

Occasionally, a few variables get errors due to concurrent instances running simultaneously. They should improve this particular area. Also, providing more specific documentation on configuration would be helpful.

We have been using the solution for three years.

It is a stable solution. I rate its stability as a ten.

The solution is scalable.

I visit online forums for technical support in case of any errors.

We used UFT earlier.

The solution's initial setup process is straightforward. You must know about the required environment and security credentials for implementation. It needs two test automation engineers and one business analyst to execute and takes a few hours to complete.

I rate the process as an eight.

The solution's price is reasonable. We pay around £70 a month for it. I rate its pricing as one.

I advise others to gain knowledge of JavaScript. It will help them use the solution's test automation framework with ease.

I rate the solution as a nine.