CI/CD (Pipeline) Clarified

There is really no need for the terms such as CD, CI/CD, CI/CD Pipeline or CT, if software professionals do CI properly. Automated End-to-End UI Testing is the key.

Image Credit: https://www.pagerduty.com/resources/learn/what-is-continuous-integration/; https://www.techaheadcorp.com/blog/how-ci-cd-save-app-development-time/

This article is one of the “IT Terminology Clarified” series.

Nowadays, nearly everyone working in software development hears one or more of the following terminologies on a daily basis:

• CI (Continuous Integration)
• CD (Continuous Delivery)
• CI/CD
• CI/CD Pipeline
• CT (Continuous Testing)

It is a bit confusing, isn’t it? This article will clarify.

Table of Contents:
· Why so many similar terms?
· Continuous Integration
· Continuous Delivery is really about testing
· Why “CI/CD”?
· CI/CD Reality 
· CI/CD Pipeline
· CT (Continuous Testing)
· Why CI is good enough if done properly?

Why so many similar terms?

First, if a software project does CI properly, there is no need for all other terms. In other words, most projects did CI badly.

The Toyota Corolla is one of the most popular compact cars n Australia, the current…