Try our new research platform with insights from 80,000+ expert users
Associate Test Engineer at OSI Consulting, Inc.
Real User
An ideal solution for single-user API testing that includes good visibility of PDF reports
Pros and Cons
  • "The solution provides visibility for PDF reports without needing to install plugins."
  • "The solution has some user interface difficulties when conducting environment collections."

What is our primary use case?

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. 

What is most valuable?

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

Other solutions like JMeter require plugins which is not ideal. 

What needs improvement?

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. 

For how long have I used the solution?

I have been using the solution for one year. 

Buyer's Guide
Postman
November 2024
Learn what your peers think about Postman. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the stability of the solution?

The solution is stable and provides a good user experience. 

What do I think about the scalability of the solution?

The solution is scalable. 

How was the initial setup?

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

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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. 

Which other solutions did I evaluate?

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. 

What other advice do I have?

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

I rate the solution a nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Test Lead at a tech services company with 10,001+ employees
Real User
It lets you share test cases with your teammates
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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. 

How has it helped my organization?

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. 

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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. 

Which solution did I use previously and why did I switch?

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. 

How was the initial setup?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Postman
November 2024
Learn what your peers think about Postman. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Kumara Swamy - PeerSpot reviewer
Software Development Engineer in Test at a tech services company with 1-10 employees
Real User
Good features, an easy setup and has the option to use a free open-source version
Pros and Cons
  • "It is stable and reliable."
  • "We'd like to see some better UI in newer versions."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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. 

For how long have I used the solution?

I've been using the solution for 11 years.

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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. 

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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. 

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Amiya Acharya - PeerSpot reviewer
Senior Automation Engineer at a tech vendor with 10,001+ employees
Real User
Top 20
An appealing solution for API regression but needs more advanced data-driven testing
Pros and Cons
  • "Postman is open-source and free to use."
  • "Postman needs more advanced data-driven testing."

What is our primary use case?

Postman is an API regression suite, and we design different workflow center processes. We maintain the Postman tool and add JavaScript applications. Since it is not that robust, like ReadyAPI, we have to write many scripts to support it.

What is most valuable?

The UI is good. It's appealing and free, and everyone can use it.

What needs improvement?

Postman needs more advanced data-driven testing. We have to provide the data filter in runtime only. It's not like software, and we can add different data sources. That feature is not in Postman yet.

For how long have I used the solution?

We have been using Postman for one year.

What do I think about the stability of the solution?

It is not that stable because the bigger the APIs, the higher the chance of crashes. Also, it takes up a lot of RAM and system memory, so it is not that reliable.

What do I think about the scalability of the solution?

It is scalable, but it takes up a lot of resources. We have 40 users using Postman, mostly from the dev, automation and manual test teams. We use the solution weekly.

How are customer service and support?

Postman has a support center, but they are not responsive. Many issues are still pending. I rate the technical support a six out of ten.

How would you rate customer service and support?

Neutral

How was the initial setup?

You complete some setup processes for an application and have to provide the URL. It is not a complex setup. With a bit of understanding of API, it can be set up. I rate the setup an eight out of ten. There is a dedicated framework team for maintenance comprising about six people. Maintenance is required every three months.

What's my experience with pricing, setup cost, and licensing?

Postman is open-source and free to use. I believe there is a corporate license they add to make it more robust and fast, but everyone mostly uses the free version.

What other advice do I have?

I rate this solution a seven out of ten. You can use Postman if you are a beginner or trying to learn API. Small-scale organizations can also use it because it does not need any license.

Postman is gaining pace because it supports the Google Chrome compatibility rate and plugin support. It is easy to set it up for the testing team. It is a good tool, but it still needs improvement for a scalable API tool.

Regarding advice, there are some secure APIs in different organizations, so it's better to get approval from your manager or architect so that APIs are not exposed. Also, it is important to be cautious about the organization's sensitive data before implementing Postman.

Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
reviewer1675566 - PeerSpot reviewer
Technical Test Lead at a tech services company with 10,001+ employees
Real User
Easy to use with strong reporting features
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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. 

How has it helped my organization?

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.

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

I've been using Postman for three years.

What do I think about the stability of the solution?

Postman has never failed. Maybe once or twice depending on my internet connection. But generally, no issues from the Postman site.

What do I think about the scalability of the solution?

We have integrated Postman with Newman, and that is working fine.

How are customer service and technical support?

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. 

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

Postman setup was straightforward. It was not complex

What's my experience with pricing, setup cost, and licensing?

It's open-source, so I don't think a cost is involved.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2148840 - PeerSpot reviewer
Automation Testing Engineer at a tech vendor with 10,001+ employees
MSP
Top 20
Easy to set up and reliable with good reporting
Pros and Cons
  • "It is stable and does not lag."
  • "Reporting can be better. If you have bigger APIs, it takes time."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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. 

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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. 

How was the initial setup?

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

What other advice do I have?

I am an end-user.

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

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Shahid Manzoor - PeerSpot reviewer
Software Quality Assurance Supervisor at a transportation company with 1,001-5,000 employees
Real User
Top 10
API building and management platform used for six years to test and manage REST APIs
Pros and Cons
  • "Postman uses the DRY framework of JavaScript and that framework is easy and a good way to put assertions on responses."
  • "Postman could be improved by providing options for performance testing of APIs."

What is our primary use case?

Postman is a good tool for completing a sanity check or smoke test of REST APIs. It's a quick way to manage your REST API-related test cases, and it gives good options for assertions for the response of the APIs. We have 30 people using this solution in our business. 

What is most valuable?

Postman uses the DRY framework of JavaScript and that framework is easy and a good way to put assertions on responses.

What needs improvement?

Postman could be improved by providing options for performance testing of APIs. We would like to complete performance testing of a specific set of API's by checking them against thousands of the records and checking responses times.

For how long have I used the solution?

I have been using this solution for six years. 

What do I think about the stability of the solution?

This is a stable solution. 

What do I think about the scalability of the solution?

This is a scalable solution.

How was the initial setup?

The initial setup is straightforward and only takes a few minutes. 

What other advice do I have?

I would rate this solution an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Arunkumar Anand - PeerSpot reviewer
Technology Specialist at a tech vendor with 10,001+ employees
Real User
The environment variables are a valuable feature because i can easily switch them and see all the developments in different cycles and stages
Pros and Cons
  • "The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages."
  • "One area that could be better is collection management."

What is our primary use case?

We use Postman for API testing only. We test it locally and share contracts with other teams. We also enter environmental variables to test different environments.

What is most valuable?

The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages. I can deploy it locally and QA everything in different environments. 

I can copy the cURL request from the browser when browsing any website, copy the network tab from the browser and import it to Postman instead of rewriting everything, which comes in handy when debugging. If I'm working with a complete browser-deployed app, I can open a specific URL and see the recursion. 

What needs improvement?

One area that could be better is collection management. I duplicate collections and end up with lots of them. Maybe I'm not using it properly. But a better way to manage and save collections would be an improvement.

Another improvement would be the ability to clone a collection (or even have cloning as the default) to avoid time-consuming production issues.

For how long have I used the solution?

We've been using the product for three or four years.

What do I think about the stability of the solution?

Postman is pretty reliable. I haven't encountered many stability problems.

What do I think about the scalability of the solution?

Only the client can test it. I do not see much use for scalability. For example, if I have all these collections, I can use some script and automate the flow. Other than that, we don't see many use cases for Postman itself. 

How are customer service and support?

So far, we've had no issues with Postman that required support because we just make an HTTP call and show the results. So we can get all the support we might need from sites like Stack Overflow.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup was straightforward with a little complexity.

What about the implementation team?

Implementation was done in-house only.

Which other solutions did I evaluate?

We tried some different solutions after using Postman, not before. But Postman has better graphical support than its peers. At that time, I tried using a product whose name I can't remember ("Fire" something, I think) and others but had problems with them, so stopped.

What other advice do I have?

I would rate this solution eight out of 10.

Regarding our relationship with the vendor, as far as I'm aware, the company has no business relationship with Postman. We use the product because it's the world's most commonly used open-source tool for repair testing.  

Regarding the number of staff required for the daily maintenance of the solution, we only make changes when the Postman tool or the contract changes. API contracts are modified daily. Most staff members continually modify or update these collections. Our developers use Postman at least once a day when developing.

My advice for others looking to implement Postman in their companies is that there is no reason to implement Postman. Plenty of other solutions are available, but most people are familiar with Postman because it appears in several YouTube tutorials. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Postman Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free Postman Report and get advice and tips from experienced pros sharing their opinions.