CI/CD is short for Continuous Integration, Continuous Deployment (or _Delivery_). It is a pipeline that takes code changes then **automatically** runs necessary steps to _build_, _test_, and (if tests pass) _package_ & _deploy_. The most basic version is - your build passes so it's packaged & deployed. The better version is your build passes, AND it passes a 100% coverage test suite, then it's packaged & deployed. CI/CD pipelines are used by any legitimate medium-to-large web application. I like them because they scaffold "the right way" to do things, and in so doing both make it **obvious** and, in theory at least, **easy** to do best practices thereafter. It's sort of the [[Pit of Success]]. You can't push obviously bad code. Also, much like [[Test-Driven Development]] in general, you are forced to specify *expected* behaviors up front, leading to increased clarity. **** # More ## Source ## Related - [[Test-Driven Development]]