AUTOMATED TESTS AS DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components ii. Test suite becomes the living documentation of the system continuous inspection, automated testing to achieve outcomes intended with controls. e. ENSURE DOCUMENTATION AND PROOF FOR AUDITORS AND COMPLIANCE OFFICERS i. DevOps challenges the traditional notions

i. Don’t practice “Mean Time until Declared Innocent” – culture of blame encourages limited documentation, hiding telemetry, deflection 1. Prevents creation of institutional knowledge about incidents incidents 1. Bad pull requests – typically doesn’t have enough context for the reader, little documentation of the changes intended outcome, or explanation of the thought process behind the change 2.

potential implications, or to merely rubber stamp their approvals c. Creating large volumes of documentation of questionable detail which become obsolete shortly after they are written d. Pushing large

3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and