Postman Enterprise Reviews

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.

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.

I'm using Postman for manual testing of REST APIs. There are some built-in collections done by some of my teammates, so I use those.

The solution is deployed on a public cloud.

I have used some parameterization from a global variable, so that was working fine for me. It's easy to see different versions of responses. There's also a possibility for automation.

We cannot do database connections from Postman directly, and we don't have a way to do that. If they could implement auto-validations and assertions from SoapUI, that would be a very good feature.

We don't have a provision to go and connect to the database from Postman. That's one drawback. If you want to automate in Postman, there is a major drawback. Being a tester, you always want to cross-verify your data with the database. If the database is not connected, then part of your testing becomes manual.

I have used this solution for about seven years.

It's stable. Sometimes it has gone off, and I have had to rebuild the collections again. I've had to switch the logins sometimes. It has crashed twice, and I lost my suites and had to build it again.

Initial setup is easy. Sometimes we get the proxy errors, but when we go to the settings and disable the proxy things, it's pretty simple. Comparatively, SoapUI is easier for me.

Maybe some people who don't have a licensed version of Postman or ReadyAPI might feel that it's easier to automate with Postman, but I'm not sure about that because I haven't done it.

I would rate this solution as four out of ten.

If you don't have SoapUI or if you don't know about SoapUI, then of course you can use it. If you want to explore Postman, it's a free tool.

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. 

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.

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. 

We are primarily using the solution for API testing. We do some automation and validation.

The solution offers automation execution. You can do automation very quickly. We can access the variables. The environment setup is over there, and we can utilize it.

We can execute validations. 

We can get reports very fast. The generation allows us to share those with end users and stakeholders. 

We can access the solution quickly via a SSO.

It can scale well.

It is stable and does not lag.

The initial setup is easy.

Reporting can be better. If you have bigger APIs, it takes time. The process should be faster and more automated. We'd like more visualizations. 

I've been using the solution for three or four years. 

I'd rate the stability eight or nine out of ten. There are no lag issues. It's easy to use and reliable. There are no bugs or glitches. 

There are multiples for API testing. The scaling is fine. I'd rate the ability to extend eight out of ten. 

The solution works well at the enterprise level. 2,000 to 5,000 people are in that company. It's quite compatible with a range of company sizes. 

I've never used technical support. I can't speak to how helpful or responsive they would be. 

We do have another tool. We are using Jmeter, among others. However, I do not like its look and feel. Postman allows for saving collections and has a nice look and feel. 

The initial setup is simple. It's not overly complex. We have a desktop version and downloaded it to laptops.

I am an end-user.

I'd rate the solution eight out of ten. I've been happy with its capabilities so far.