Postman removes a lot of the pain of testing http-based API projects
June 18, 2019

Postman removes a lot of the pain of testing http-based API projects

Anthony Aziz | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Postman

We use Postman to directly develop and test our APIs. We use it to easily run requests against our own API features in development, run test suites for automated testing, interact and test external web services, and perform maintenance tasks on our APIs where a UI isn't required.
  • Shared team library
  • Save collections of common requests
  • Set up mock servers and mock requests for testing
  • Set up test criteria and scripts
  • UI can be a bit cumbersome
  • Test features is not as fully fleshed out as other automated testing tools
  • Improves development time by not requiring engineers to build interfaces for testing, or use convoluted tools.
  • Improves reliability of codebase by allowing automated API test suites.
  • Sharing collections within the team drastically reduces workload of operational and maintenance tasks by saving common requests.
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.
Postman is extremely useful when developing any web-based service, such as RESTful APIs. Particularly when you need to repeat requests, either while iterating overdevelopment, or when doing automated testing. Postman doesn't have any browser rendering, so it is not suitable for testing or mocking front-end UIs. However it is a great tool for bypassing these UIs to test the backing service.

Postman Feature Ratings

API versioning
Not Rated