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.

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 this solution for every API development.

We are exploring code generation and how it works. We also like the test functionalities and snippets that we can use directly.  

Moreover, the tool is simple and easy.

Integration should be improved with our continuation system because we use Azure DevOps separately.

I have been using Postman for around two years. Initially, we used it only once, and now we use it more.

The solution is stable.

The solution is easy to scale till now.

We are using the solution for five people.

We get help from videos and the web.

Positive

We have also worked with SoapUI, but we like Postman because it has automation.

Postman is a more compact tool, and it has many functionalities. In the first stage that we used, Postman, we only tested how it works. Now we are using more functionalities. With SoapUI, it's because some customers have used it to define the APIs, and then we have to interact with this environment.

But we use Postman, and we prefer Postman. Although, there are some tools from SoapUI that are good. For example, the API design, checking, and definition. If Postman has anything similar, you can check the definition of the API, and it proposes you an improvement and so on, but in the development phase, we used Postman, and we like Postman.

The solution’s initial setup is easy. The maintenance is easy as well because we are not doing all the possible accents and because we are not doing anything to maintain.

The solution is deployed on the public cloud and on-premises in our organization. But I use it more in the cloud.

The solution’s pricing is realistic according to our usage level. As we grow and require additional functionality beyond what we currently use, there is a higher cost while upgrading the developer plan. We want to explore features like automatic code generation and other functionalities.

We are paying only for the license for now, and it comes with a monthly subscription.

Postman is one of the most widely used tools in the market. When you use it, it is practical and useful. You need to check whether it suits your team, project type, and work to take profit from the way Postman works. From the beginning, it is one of the three main tools you must explore if you regularly deal with APIs.

However, I am still exploring all the tools, and I don't know if I can maintain it or not. When I know all the different technologies better, I will be able to say.
Overall, I would rate the solution an eight or nine 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.

Postman is a scripting tool.

I started using the solution when we did an SDN-based network implementation from Cisco. I got introduced to a particular scripting tool where I could actually put down everything in an Excel sheet. And if I want to configure, for example, ten ports, then I can actually do the configuration of everything in an Excel sheet. I can pass my credentials in Postman, and I can import the SQL script, and based on whether it's an infrastructure script or a configuration script, I can actually save it in Postman.

I'm using Postman to only push the scripts into the ACI, and that is a very limited use of Postman that we do right now.

I'm sure it might have other usages. That said, we have not explored other features beyond that at this point in time.

The initial setup is easy.

The solution is stable.

It is very user-friendly and has a nice UI.

My limited use of Postman has been to get the output of scripting in Postman or get the output from APIs and then open it in Postman or post the script. We don't use it much beyond that and therefore haven't really explored the features. It's hard to say what is lacking.

Postman does not have a check-in balance. Essentially what I mean by that is if there is something that is already configured on a particular device, it just overrides it without checking whether you really want to override it or not. Even if it is by mistake, if there is a dialogue box that is available before it overrides, it's just a much nicer feature to be notified if you're doing something by mistake.

I've been using the solution for a while. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. We haven't faced any issues.

I know that our team, which is three people, uses the solution. I'm not sure who else does in the company. We're all engineers. 

We have received all of the support we required. Postman has a very good team.

We use quite a few products from an infrastructure point of view. We use SolarWinds, both for server and infrastructure capacity, and we use a change management and a problem management tool. From a bandwidth monitoring perspective, we use a network analyzer; we use Splunk heavily. We do a lot of scripting tools using Postman and Python.

I'm more into Python since Python gives us many more API interjections and compatibility with a lot of other APIs. We started using Postman, and then we immediately moved to Python-based scripting.

The functionality that Python gives you concerning the available APIs and then the ability to put that in the Excel sheet is much better than Postman.

The solution is very easy to set up. There were no issues. 

I don't deal with the licensing aspect of the product. 

We looked into other solutions. However, Cisco actually recommended Postman, so we went with this product. 

I'm an end-user.

I'm not sure which version of the solution I'm using. 

New users need to watch a few videos and understand the solution pretty well. If you are using Postman for the first time, never use the administrative credentials. It is very easy for you if you're using the administrative credentials to pass through the Postman's scripts. It is possible that you might override the configuration unknowingly. If that happens, that can actually bring down a good amount of your configuration or an earlier configuration. It's best to actually get the solution into a development environment before you actually do anything on production.

I'd rate the solution seven out of ten. It's a good, very user-friendly scripting tool. Anybody can learn it and start using it. However, new users do need a little bit of knowledge and must be willing to learn as they go.

We primarily use the solution for testing and preparation of the base URL which I generated for the first tokenization. I prepare the test suite and the XML or Java core that give the input parameters.

The major role is the pre-requisition of the scripts in Postman - which is mandatory.

We can input parameters into Excel and execute for the application.

We work in many environments, including QA, SAP, production, pre-production, and proof. We use Postman for each and every release.  

Before anything goes to the master branch in GitHub, I'll completely check the code and unit test the complete scripting. I'll execute it one or two times, and once it's stabilized, I'll directly deploy it to the master branch.

The output has been very good.

There are lots of good features. 

Its initial setup is easy, depending on the operating system.

It is stable and reliable. 

The product is not expensive, although there is also the option for open-source, so it can be free to use.

We need better version compatibility. In open-source, the main drawback is when you go to integrate the plugins, it is entirely scripted. Sometimes the scripts aren't scripting.

The execution time should only be two or three seconds. 

We'd like to see some better UI in newer versions. 

I've been using the solution for 11 years.

The solution is stable. Before we deploy, we can check in for the local system. Once it is successful, then we'll go for the server side. That is a good practice to follow.

There are no bugs or glitches. It doesn't crash or freeze. 

We have 13 people using the product. It's just my team using the solution, as we have maintained the SSL certification separately.

I'm already an expert in the product and therefore do not need to contact technical support for help. If I have issues, I can troubleshoot on my own.

We chose this solution based on the project. Typically, the client requests something, and, depending on the client and the project's needs, we'll use what makes sense. We use the best tool for the job. If it happens to be this solution, then we use it. If it's something else, we use something else. 

If a file is in Windows, it is very easy to deploy the product. We can do configurations easily and handle test scripts well. It's all very straightforward.

However, other operating systems may be more difficult. The process varies depending on if you are using Windows, Unbuntu, or Linux, for example. 

Depending on the scripting, the deployment hardly takes 30 seconds to one minute. It'll check for the E2E level in the checkpoints, and how to trigger in the checkpoints.

The solution has both open-source and licensing options. You can pay for monthly licensing. However, that's not always necessary. There are also plugins that are available that we can implement. It's not an expensive product, even if you go for the license. They do have multiple licensing options as well. They have options for freelancers and mid-sized businesses as well as larger businesses. 

We are a Postman partner. 

I've been using an older version of the solution. I'm not on the latest deployment.

I'd advise others that it is important to have project middleware functionality, including for the access level. When I work with clients, I will ask for the certifications of the tool. Once the tool is initiated, 99.9% of the time,  there is no management involvement here. It's signed off on.

I'd rate the solution nine out of ten.

Our company uses the solution for single user regression testing of APIs. For each of our releases, we run a regression report that includes APIs contained in that release. 

We create structure suites by importing API information from swagger links, writing test scripts for APIs, and validating the values in our responses. This process can take some time but completed ignition suites can be reused. 

The solution provides visibility for PDF reports without needing to install plugins. 

Other solutions like JMeter require plugins which is not ideal. 

The solution has some user interface difficulties when conducting environment collections. 

It is important to be careful when storing information to ensure files are secure and not lost. Storing information can be a bit hectic. 

I have been using the solution for one year. 

The solution is stable and provides a good user experience. 

The solution is scalable. 

The initial setup is quite easy because installation automatically sets up collections. 

Our company implemented the solution which requires manually writing the process. 

The solution has a licensing fee which might be prohibitive.

There are open source options that are cost effective and offer API testing such as JMeter. 

If JMeter is too restrictive based on your project, then I suggest moving to the solution. 

We use the solution for attrition and single user testing of APIs. 

We use JMeter for automated API testing and load testing for multiple users. 

The solution requires an awareness of APIs, JSON format, XML format, schema, and Java scripting. 

I rate the solution a nine out of ten.