What needs improvement with 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.

Postman is a bit more of a complex tool, making it an area where improvements can be made. Postman is good the way it is right now, so there's nothing to change in it.

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.

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

I would like to see more integrations with other platforms.

They should integrate the solution with Salesforce.

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.

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.

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.

The reporting could be better. It should give you a detailed PDF report after you run a test.

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 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.

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.

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.

Postman could improve the saving date capabilities.

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.

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.

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.

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.

It would be better if we could integrate programming languages like .NET, Java, and JavaScript. It could also be more user-friendly.

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.

We have previously used Tosca which allowed us to verify information using authentications. It would be useful if this was also possible using Postman. In a future release, Postman should connect to DB.

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.

The request encryption could be one thing on which they can work a little bit. If we don't want to expose our production data but we still want to test our APIs on the production data, there should be a way to do that. It is not only with Postman. I think no tool in the market is doing that right now. It would be helpful if better tutorials or recommendations are available while we are using the product. Otherwise, we have to go out and search for specific things. It would be good if they build something in the tool itself that provides recommendations based on the task that we are doing. If we are testing APIs, the tool should come up with some kind of information. Scalability-wise, it can be improved a little bit. They can include more options to do the performance testing or rate testing so that we can query or push a lot of requests to our APIs. There could be some kind of graphical interface for performance testing. It would be really helpful if it can give some data to visualize how the performance testing is going in real-time, but there are specific tools for that. Postman might not be meant for that, but they can think on those lines.

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.

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 have recently noticed that, for some reason, I am not able to import collections in JSON. It is weird because I was able to do it before. When you create a new collection and documentation, in tests, you usually have to click Save. If you don't click Save, your collections don't sync with other devices, which is something I don't like. It is not clear for the users in a shared workspace, and I usually forget to click Save and end up losing all the collections that I created. I create a lot of routes, and clicking Save all the time isn't efficient. Instead of clicking Save all the time, there should be an option to save everything in one go.

Actually, I received some errors regarding the testing of SOAP APIs. There's definitely some space for improving the user's experience. There needs to be more flexibility surrounding the testing of SOAP APIs. Currently, they are primarily based on JSON files — invest APIs actually. I know that SOAP APIs are considered a little outdated but they're still in use. Unfortunately, because of this, I have to search for another solution that supports SOAP APIs, because Postman doesn't.

An area that needs some improvement would be to allow multiple windows with different collections to be open at the same time. It only allows you to open one with the same collection. If we open a new Postman window, it does not allow me to have the same collection as I had in the previous window. Allowing us to have replicas of the same collection open independently would be helpful. I would like to see if it can incorporate Jenkins integrations.

The solution can be confusing for first-time users so it could be made a little more user friendly. It's just click and proceed but still confusing if you haven't used it before.

In terms of what can be improved, I would expect extra features that would make our work easier. I just saw that it's functioning is based on the machine. Meaning, if we have a certain build on one machine it won't work with another build even if we are using the same URL. It would give us a connection refuse. So developing environment compatibility would make it better. Other than that, I don't see anything more to improve. As it is now, I get for a return whatever I am expecting. That's why I gave it a seven or an eight. Because I'm not expecting much on that portion. Because, we are mostly focused on that I would expect more validation points.

The pricing should be adjusted for the Pro plan.

When you get a response, for example, if you search the response and want to know how many numbers of fields, it displays 10 times. If a purchase has five to 10 cards in the response, instead of one of the fields being mandatory, it has to be part of each section of the cards. I would like that if you click on one of the fields you should be able to see the entire row of fields, names, and values.

I have display issues in my Windows that need to be fixed.

We would like to create an entire suite where we can check the contents of the definition, like the server file. It should be able to check the records and compare them to the regression testing more on the automation side. We cannot see transaction times in the product.