Don't do that. •Code Review •Automated Tooling - part of CI107 How can we test it? 1. Historical Audit of Enum Values (Version Control Tracking) 2. Enumeration/Constant Versioning and Deprecation 3. Through Code Review Process 9. Symbolic Constant Tracking108 How can we test it? 1. Historical Audit of Enum Values (Version Control Tracking) 2. Enumeration/Constant Versioning and Deprecation 3. of same thing •Monitor and SMARS had different cumqty •Validate different system views •Event Logs122 How can we test it? •Remove old code and add new code at the same time •Reuse an existing "value"

latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables 146 Chapter 5. Devops guide Conan Documentation, Release 2.0.17 • The associated to the package binary for a given specific configuration and represented by a package_id. Build logs, tests reports, etc, that are specific to a binary configuration will be package metadata. 5.3.1

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables 150 Chapter 5. Devops guide Conan Documentation, Release 2.1.0 • The tests

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like

metadata files associated to recipes and packages. This feature can be very useful to manage build logs, tests executable, test results, coverage data and many other different files needed for traceability latest changes in the upstream main fork of conan-center-index into your fork. • You can check and audit those changes if you want to, analyzing the diffs (some automation that trims the diffs of recipes could be very important for compliance, technical or business reasons, for example: • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like