Except Data Generator and Database connectivity, happy with Postman
April 28, 2022

Except Data Generator and Database connectivity, happy with Postman

Haroon Akmal | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Postman

We're using Postman for testing of our API systems. We've got many different API systems, public and private, and all those systems are tested by my team using Postman. We've created different collections for each, as Smoke tests, that we run at each test-deploy and then we also have Functional tests collection. We're continuously maintaining these tests (collection). The problem I've is that it lacks the connectivity with databases, either relation or trendy-document DB like MongoDB/ CosmosDB. I have to rely on exporting data from these DBs and to feed it in Postman. This is the only manual step a user has to perform, otherwise our tests are based fully on automation.
  • Loading APIs (Just put the URL and hit send, if it doesn't require security token)
  • N-level of organizing collections into folders/ sub-folders
  • Sharing the collection across team
  • Create documentation, adding examples for each scenario
  • Run Feature
  • Assertion scripts snippets are really helpful in tests
  • Environments can be organized as per users' need.
  • Database connectivity - To get data directly from DBs (traditional plus new like MongoDB or CosmosDB)
  • Data Generator - Random data generator like email, names, zip/postal codes, addresses, mobile number. Although there's a public API but it has limits.
  • Sharing
  • Documentation
  • Monitors
  • A lot of manual human effort is replaced by quicker automation
  • Monitor keeps eye on critical endpoints
Sharing across teams is very robust in Postman than SoapUI.
Adding APIs/ managing collections is very user friendly in Postman.

Do you think Postman delivers good value for the price?


Are you happy with Postman's feature set?


Did Postman live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Postman go as expected?


Would you buy Postman again?


Postman is well suited where APIs are involved. I've been testing many backend systems and are well organized into many tests like Smoke for each system and then functional tests as well. Along with that I've few created monitors for production-critical endpoints/API-methods.

Postman is less appropriate where you need to automate your tests that involves verification from databases or depends on data from databases. Also, it lacks functionality to generate random data. I've been using work around using scripts to achieve randomness in my tests.

Postman Feature Ratings

API access control
Usage billing and payments
Not Rated
API monitoring and logging