I did a quick write-up on how we utilize continuous testing and deployment validation at Assertible (article: https://assertible.com/blog/test-every-single-api-deployment)
Our continuous testing workflow is part of our bigger CI setup. Generally, it looks like:
- Push code to hosted repo (GitHub)
- CircleCI pulls code, builds tests and executables
- Scripts deploy the new code to staging
- Automated API tests and validations are run to ensure the correctness of this deployment.
Obviously, if a test doesn't pass on staging, the PR can't be merged and the code can't go into production. Having this process makes it simple to quickly validate and test new API releases, save a ton of time from manual testing, etc.
While writing, I became interested in hearing how other teams test and validate deployments of their web services.
Does your team do this? Why or why not? What does your pipeline look like?
Full article: https://assertible.com/blog/test-every-single-api-deployment
I did a quick write-up on how we utilize continuous testing and deployment validation at Assertible (article: https://assertible.com/blog/test-every-single-api-deployment)
Our continuous testing workflow is part of our bigger CI setup. Generally, it looks like:
Obviously, if a test doesn't pass on staging, the PR can't be merged and the code can't go into production. Having this process makes it simple to quickly validate and test new API releases, save a ton of time from manual testing, etc.
While writing, I became interested in hearing how other teams test and validate deployments of their web services.
Does your team do this? Why or why not? What does your pipeline look like?
Full article: https://assertible.com/blog/test-every-single-api-deployment