Postman vs. Microsoft Visual Studio

Postman is very good for easy entry into testing. Thanks to snippets it is easy to use, but also provides a lot [of] possibilities for testing thanks to the in-line editor. Easy to use on multiple environments (versioning) thanks to sets of environment variables. The Collections view can get very full with time and it is not possible to reuse or link requests so that they have always been copied and maintained manually for each copy if changes have to be applied.

It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.

• It has opened a door for me to explore more out of it, as it is associated with so many APIs that I never felt any difficulty in finding the right API template, which are well organized and easily available.
• It is very secure to use and provides great services which are user-friendly.
• Due to this software I have got rid of the excessive emails and the slack channels, Now I am using my own private API and even it give me an option to produce my personal Postman’s API Builder from its Private API Network and this features has shared my excessive workload.

Incentivized

• Since Microsoft offers a free Community Edition of the IDE many of our new developers have used it at home or school and are very familiar with the user interface, requiring little training to move up to the paid, enterprise-friendly editions we use.
• The online community support for Visual Studio is outstanding, as solid or better than any other commercial or open-source project software.
• Microsoft continuously keeps the product up to date and has maintained a history of doing so. They use it internally for their own development so there is little chance it will ever fall out of favor and become unsupported.

Incentivized

• Wherever you need to automate tests that involve database verification or rely on data from databases, Postman is less suitable.
• Postman's disc usage is extremely high, and it occasionally causes the computer to fade.
• It doesn't have the ability to generate random data. To achieve randomness in my tests, I've been working around scripts.

• Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
• Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.

Incentivized

VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.

Incentivized

I think from a non-technical perspective there are a few things that could be more clearly labeled to better understand what is being asked for or where to add certain parts of the request.

Incentivized

The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.

Incentivized

There is a lot of in-depth documentation for Postman available online, including detailed guides with screenshots and videos. They provide example APIs for new users to explore while learning how to use the tool. Generally, bugs in the client are quickly addressed through frequent free updates. Community and professional support options are available - most of the time, the free/community level support is adequate

Incentivized

Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.

Incentivized

Previous to using Postman, I would either use browser tools directly, or write an in-house tool to send requests. Postman eliminates that need while providing a much better experience and more features. At the base level, Postman is as simple as typing in the address as you would in a browser. Authentication can be provided simply as well.

Incentivized

I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.

• Postman is free (although there's a paid tier that offers more features) so using it for testing APIs comes with little to no risk (besides learning curve).
• The learning curve is a little steep for non-developer users, but developers should find it easy to pick up and use right out of the box, so to speak.

Incentivized

• We've had hundreds of hours saved by the rapid development that Visual Studio provides.
• We've lost some time in the Xamarin updates. However, being cross platform, we ultimately saved tons of time not having to create separate apps for iOS and Android.

Incentivized