Summary
Your website's Bicep deployments sometimes failed because of problems you introduced in your Bicep files. You wanted to add quality control to your deployment workflow, to reduce the likelihood of any problems affecting your production website.
In this module, you learned how to add validation and tests to your Bicep deployment workflow. You learned about multi-job workflows, and how to create workflow jobs to lint and validate a Bicep file. Then you learned how to add a preview job to your workflow, which runs the what-if command and asks for human verification before the workflow continues. Finally, you learned about the importance of functional testing, and you added a test to verify that your website meets your security team's requirements after every deployment.
Now, you can be more confident that your automated deployments will succeed and that they won't cause problems for your environments.
Related content
- Shift testing left with unit tests
- GitHub Actions
- GitHub Actions expressions
- Use Bicep linter
- GitHub Actions environments
- About protected branches
- What-if operation
- Testing