Continuous Delivery

Ch. 3: Continuous Integration

Definitions and Terms

unit tests - (pg 60) - test small pieces of your application in isolation; they run without starting the whole application
component tests - (pg 60) - test the behavior of several components of your application; they may hit the database, filesystem, or other systems (which may use stubs); Component tests typically take longer to run than unit tests.
Acceptance tests - (pg 60) - test that the application meets the acceptance criteria decided by the business in terms of behavior, security, and performance; Acceptance tests run against the whole application in a production-like environment

Version Control - Anything needed to create, install, run, and test your application
Automated Build - Able to "start your build" from the commandline
Agreement of the Team - "Continuous integration is a practice not a tool"

"ten minutes is about the limit, five minutes is better, and about ninety seconds is ideal"
two stages: "commit" and...unnamed stage in which acceptance tests run
commit stage runs for every checkin
acceptance stage runs after commit stage (not clear if this is gating)
incorporate smoke tests into commit stage

Dashboards: builds status + avatars
"Visibility is one of the most important parts of a CI server"
source code analysis
- coverage
- duplication
- standards
- cyclomatic complexity