OPS05-BP02 Test and validate changes
Test and validate changes to help limit and detect errors. Automate testing to reduce errors caused by manual processes, and reduce the level of effort to test.
Many AWS services offer version control capabilities. Use a revision
or source control system such as
AWS CodeCommit
Common anti-patterns:
-
You deploy your new code to production and customers start calling because your application is no longer working.
-
You apply new security groups to enhance your perimeter security. It works with unintended consequences; Your users are unable to access your applications.
-
You modify a method invoked by your new function. Another function was also dependant on that method and no longer works. The issue is not detected and enters production. The other function is not invoked for some time and finally fails in production without any correlation to the cause.
Benefits of establishing this best practice: By testing and validating changes early, you are able to address issues with minimized costs and limit the impact on your customers. By testing prior to deployment you minimize the introduction of errors.
Level of risk exposed if this best practice is not established: High
Implementation guidance
-
Test and validate changes: Changes should be tested and the results validated at all lifecycle stages (for example, development, test, and production). Use testing results to confirm new features and mitigate the risk and impact of failed deployments. Automate testing and validation to ensure consistency of review, to reduce errors caused by manual processes, and reduce the level of effort.
Resources
Related documents:
