Menu

Most 'CI/CD' Setups Are Actually Just CD, the Testing Got Skipped
πŸ“°

Most 'CI/CD' Setups Are Actually Just CD, the Testing Got Skipped

DEV Community: cicdΒ·Sherdil CloudΒ·3 days ago
#GnkcFdaO
#devtocicd#devto#dev#pipeline#test
Reading 0:00
15s threshold

TL;DR: A pipeline that builds and deploys automatically but only runs a thin smoke test, or tests inconsistently across stages, isn't really "CI/CD," it's continuous deployment with continuous integration's name borrowed. The practice that actually earns the name, testing automatically and comprehensively at every stage, is also the one quietest to talk about, because "we added more tests" doesn't demo as well as GitOps or progressive delivery. A Dubai proptech team's change-failure rate dropped from 25% to 5% specifically because this gap got closed, not from any deployment-mechanics change.

Ask a team with a mature-looking pipeline whether they have "good CI/CD," and most say yes, pointing at automated builds and automated deploys. Ask a more specific question, does every change get tested at the unit, integration, and end-to-end level before it ships, automatically, every time, and the answer gets noticeably less confident.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.