Information Technology Reference
In-Depth Information
when the code is checked into the version control repository)
instead of during late-cycle testing.
•
Health of software is measurable
—By incorporating continu-
ous testing and inspection into the automated integration pro-
cess, the software product's health attributes, such as complexity,
can be tracked over time.
•
Reduce assumptions
—By rebuilding and testing software in a
clean environment using the same process and scripts on a con-
tinual basis, you can reduce assumptions (e.g., whether you are
accounting for third-party libraries or environment variables).
CI provides a safety net to reduce the risk that defects will be intro-
duced into the code base. The following are some of the risks that CI
helps to mitigate. We discuss these and other risks in the next chapter
.
• Lack of cohesive, deployable software
• Late defect discovery
• Low-quality software
• Lack of project visibility
Reduce Repetitive Processes
Reducing repetitive processes saves time, costs, and effort. This
sounds straightforward, doesn't it? These repetitive processes can
occur across all project activities, including code compilation, data-
base integration, testing, inspection, deployment, and feedback. By
automating CI, you have a greater ability to ensure all of the following.
• The process runs the same way
every time.
• An ordered process is followed. For example, you may run inspec-
tions (static analysis) before you run tests—in your build scripts.
• The processes will run every time a commit occurs in the version
control repository.
This facilitates
• The reduction of labor on repetitive processes, freeing people to
do more thought-provoking, higher-value work
