Postman vs. Stoplight

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.

API mocking, testing, and sharing are all built in functions for StopLight that work quite well. They even have functionality for generating OAI and RAML code as well, which is a huge plus. AS for as areas where StopLight is not appropriate, if you're doing anything other than API testing, StopLight may not be appropriate for use.

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

• OpenAPI support
• Markdown supports
• Git integration

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.

• Simplicity of set up. Although it's not difficult, there are tools out there that are easier to set up for testing endpoints.
• Again, it's perfectly functional, but some competitors I think have a more user friendly UI to them.

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

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'd like to also throw Runscope and Fiddler into the mix. Between StopLight and all these competitors, we've chosen StopLight primarily for the support, ease of use, and reliability. Most tools out there today are top-notch, so it really comes down to personal preference and different use-cases. Having used other API testing frameworks, StopLight definitely stacks up against the competition.

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

• Increased efficiency
• Improved comminication between backeend and frontend

Incentivized