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

Continuous Testing Pipelines

In short

Continuous testing means the right tests run at the right moment: a quick check on every commit, a deeper one on merge, the full suite every night. Fast feedback without skipping safety.

Bringing together everything from this phase — automated tests, parallel execution, containerized environments, and reporting — into a single, reliable pipeline that runs continuously with every change.

The purple blob checks toy cars with a magnifying glass at stations along an assembly line.

Think of it like this

Checks along the assembly line

A car factory doesn't inspect cars only at the exit gate. A quick check at each station catches a loose bolt before the doors go on. Your pipeline puts small, fast checks early and the slow, thorough ones later.

Watch it happen

Which tests run when

Commit

Pull request

Merge

Nightly

Production

1/5Lint and unit tests run in a few minutes. The developer hears about mistakes before getting chai.

The big ideas

What you need to know

Fast first

The earliest stages must be quick. If a PR check takes an hour, people stop waiting for it.

Tag your tests

Tags like @smoke and @regression let each stage pick the right subset without separate projects.

Many kinds of test

Unit, API, UI, accessibility, security scans and performance all have a slot in the pipeline.

Testing never stops

Even after release, monitoring and synthetic tests keep checking the live app for you.

See it in code

Walk through the code

yaml

1on:2  pull_request:3  schedule:4    - cron: "0 1 * * *"   # every night at 01:00 UTC5jobs:6  smoke:7    runs-on: ubuntu-latest8    steps:9      - uses: actions/checkout@v410      - run: npm ci && npx playwright install --with-deps && npx playwright test --grep @smoke11  regression:12    if: github.event_name == 'schedule'13    runs-on: ubuntu-latest14    steps:15      - uses: actions/checkout@v416      - run: npm ci && npx playwright install --with-deps && npx playwright test

1/3Two triggers: every pull request, and a nightly cron schedule.

One workflow, two speeds: tagged smoke tests on every pull request, the full suite only on the nightly schedule.

Save yourself the pain

Common mistakes

Oops

One giant job that runs every test on every commit.

Do this instead

Split by speed and risk: quick checks early, thorough checks later or on a schedule.

Oops

Nobody looks at the nightly run, so failures sit for weeks.

Do this instead

Send nightly results to a channel and make someone responsible for checking them each morning.

Your mission

Design your pipeline

~20 min

Quick check

Your full UI suite takes 90 minutes. Where should it run?

Go deeper

1Design a full continuous testing pipeline diagram incorporating this phase's concepts.
2Learn why a mature continuous testing pipeline is a competitive advantage for shipping quickly and safely.
3Practice explaining the value of this investment to a non-technical stakeholder.