Postman vs. CucumberStudio, from SmartBear

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.

HipTest is good and helpful to create and run functional regressions but it is more complicated to use this tool to create and run API testing scenarios (it does not mean it can not be done). This tool is definitively not appropriate for running performance testing scenarios.

Incentivized

• 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

• Good integration with Jira
• Includes integration with different tools for different porpuses
• You can build your own framework to automate scenarios and make it work with Hiptest

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.

• UX is not too obvious and easy (like generating a data table in a scenario or including a scenario in a test run) but you can get used to it relatively easy by playing around with the options, also the documentation is helpful.
• To get extra functionalities you have to pay for them separately.

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

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

The tool includes a basic but complete documentation that can be very helpful to get started using the tool. The UX sometimes does not feel very easy to understand but after some use you can get familiar without reading the documentation. The webinars are not very useful for using the tool, I have seen a couple of them and they are actually focused on promoting their HipTest product to new users instead of being useful and educational for current users.

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

• 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

• It helps to have organization in our scenarios.
• It helps to get regressions done faster than doing it manually
• It helps to graphically see the progress and results of executions.

Incentivized