Stop 11 · CI/CD & DevOps for QATopics · 1/8

CI/CD Concepts for QA

In short

Teams now ship code many times a day. Nobody has time for a two-week manual test cycle before each release, so your tests have to run on their own, every single time.

Continuous Integration merges and tests code frequently to catch issues early; Continuous Delivery/Deployment automates getting tested code into production — QA's automated tests are what makes this safe.

The purple blob tastes a fresh roti off the tawa before placing it on the serving tray.

Think of it like this

The hostel mess taste check

A good mess cook tastes every batch of dal before it goes to the counter, not once at the end of the month. CI is that taste check on every change. CD is the counter that only serves batches that passed.

Watch it happen

One code change on its way to users

Commit

Build

Unit tests

E2E tests

Staging

Release

1/6A developer pushes a small change. This push is the trigger for everything after it.

The big ideas

What you need to know

Continuous Integration

Everyone merges small changes often, and each merge is built and tested automatically. Problems show up within minutes, not weeks.

Continuous Delivery

Every passing build is ready to release. A human still presses the final button.

Continuous Deployment

Every passing build goes live automatically, with no human button. Your tests are the only gate left.

QA's new job

You design the checks the pipeline runs, keep them fast and trustworthy, and decide what blocks a release.

How it works

What you do when the pipeline goes red

1
Read the failure
Open the failed job, find the first failing test and its error message.
2
Real bug or test bug?
Check the screenshot or trace. Decide if the app broke or the test is wrong.
3
Tell the right person
Ping the developer whose commit broke it, with the link to the failed run.
4
Keep main green
The team fixes or reverts quickly so everyone else can keep merging.

Save yourself the pain

Common mistakes

Oops

Thinking CI/CD means QA is no longer needed.

Do this instead

CI/CD makes QA more important. The pipeline is only as safe as the tests you put in it.

Oops

Putting every slow test into the pipeline that runs on every commit.

Do this instead

Keep the per-commit checks fast. Run the long regression suite nightly or before release.

Your mission

Map a real pipeline

~20 min

Quick check

What is the main difference between Continuous Delivery and Continuous Deployment?

Go deeper

1Diagram a basic CI/CD flow and mark where automated tests fit in.
2Learn why fast, reliable automated tests are what actually makes CI/CD trustworthy.
3Understand a flaky or slow test suite can undermine the entire CI/CD value proposition.