Posting on behalf of a user:
Wondering if you can shed some light on this issue we are having. I have followed multiple guide (including your own https://learning.getpostman.com/docs/postman/collection_runs/integration_with_travis/) but none seems to actually be testing the current code.
For example, in the link above, this tests if https://api.coindesk.com…… can get the bitcoin exchange rate. This doesn’t appear to be testing that the current code that’s being deployed by travis is working as expected. Since postman will be testing HTTP requests, in order to test the current code, the current code needs a URL that postman/newman can run the tests against right? How can we do this?
Our current setup, is during the travis deployment, we deploy our code to another lambda stage, which we already know the urls of, and these are preset within postman. Therefore when travis is deploying it runs the tests against the code we have deployed during the travis deployment. But this means deploying code twice and seems way overkill.
So my question is, how can we use postman to test current code in CI/CD pipelines?