4 ms·

My company’s product is an API and Postman has been a key tool to test it, collaborate internally on requests and share it to the external world. Our ecosystem

by ynouri 5y ago

My company’s product is an API and Postman has been a key tool to test it, collaborate internally on requests and share it to the external world. Our ecosystem is also very API intensive and we also use Postman to discover other companies APIs. We use all those features: - HTTP requests - Mock servers (to test async requests which call back a webhook endpoint) - Workspaces: private and public - Monitors, alerts and integrations I’m excited by the direction Postman has been taking over the years. Most of commenters in the thread seem to think that Postman is still in the “lightweight cURL replacement GUI” market, like so many of the alternatives mentioned. I think this is wrong - Postman has now has moved to an upper market where requirements are more advanced and complex. Btw - we use both Postman & cURL

lysium 5y ago
How do you do version control with your postman scripts? That was the biggest issue on my last project. Plus, if the API moves, we had to (manually) find and fix dozens of Postman tests. I'd appreciate it, if you have some insights that can move my team forward.
- ynouri 5y ago
  We face a similar situation and we sometimes introduce API changes that break the monitors, which then requires to manually fix the testing script. The pain hasn’t been big enough yet to make us search for a different solution. Note that we are using Monitors mostly for end to end, user like tests, which represents a small fraction when compared to our unit test suite covering the API (where tests tend to be quite E2E as well). We do use the one way Postman -> Github integration though. Every time a change is done, it is committed to a dedicated Github repo. We use it as a backup in case anybody messes up the scripts
  - a85 5y ago
    You can do a 2-way sync now! https://blog.postman.com/the-reimagined-api-first-workflow-for-developers/ https://blog.postman.com/the-reimagined-api-first-workflow-f...
- a85 5y ago
  We introduced two-way sync with GitHub, GitLab, BitBucket etc recently so you can keep your Postman collections inside version control while being able to work with them inside Workspaces. Details here: https://blog.postman.com/the-reimagined-api-first-workflow-for-developers/ https://blog.postman.com/the-reimagined-api-first-workflow-f...

by ynouri 5y ago

lysium 5y ago

How do you do version control with your postman scripts? That was the biggest issue on my last project. Plus, if the API moves, we had to (manually) find and fix dozens of Postman tests. I'd appreciate it, if you have some insights that can move my team forward.

ynouri 5y ago
We face a similar situation and we sometimes introduce API changes that break the monitors, which then requires to manually fix the testing script. The pain hasn’t been big enough yet to make us search for a different solution. Note that we are using Monitors mostly for end to end, user like tests, which represents a small fraction when compared to our unit test suite covering the API (where tests tend to be quite E2E as well). We do use the one way Postman -> Github integration though. Every time a change is done, it is committed to a dedicated Github repo. We use it as a backup in case anybody messes up the scripts
- a85 5y ago
  You can do a 2-way sync now! https://blog.postman.com/the-reimagined-api-first-workflow-for-developers/ https://blog.postman.com/the-reimagined-api-first-workflow-f...
a85 5y ago
We introduced two-way sync with GitHub, GitLab, BitBucket etc recently so you can keep your Postman collections inside version control while being able to work with them inside Workspaces. Details here: https://blog.postman.com/the-reimagined-api-first-workflow-for-developers/ https://blog.postman.com/the-reimagined-api-first-workflow-f...