#honkotonk
1 messages · Page 1 of 1 (latest)
Hi
This strongly depends on how you are designing your CI/CD, one of the options is to deploy an endpoint for your webhook in a staging environment and do like e2e tests....or you can mock stripe webhook calls when doing your integration tests
Mmm. Our tests are codeception acceptance tests running setup by a github action in an virtual ubuntu system. I dont know how this instance could be addressed from outside by a stripe webhook.
For first option, I meant by creating a staing deployment, not in the CI pipeling it self... you run test post deployment on that env
I don't think you can cleanly do that, as GitHub does not allow you to setup webhooks directly to the container where you run your tests. What I personally do is that the integration tests running on Actions are not about webhooks, but I do have a "test mode" on dev, after deployment.
So webhooks don't stop deployment to dev, but the deploy to prod action triggers the webhook test on dev instance that was deployed
Yes something like that