Stop 04 · SDLC, Agile & Testing MethodologiesTopics · 9/9

Continuous Testing Basics

In short

Teams that release every day can't wait for a weekly test run. Continuous testing runs automated checks on every code change, so feedback arrives in minutes.

Running automated tests continuously throughout the development pipeline, not just at scheduled intervals — providing fast, constant feedback on code quality as changes are made.

The purple blob in a kitchen looks up at a ceiling smoke alarm while a pan smokes lightly on the stove.

Think of it like this

The kitchen smoke alarm

A smoke alarm doesn't wait for a weekly inspection. It watches all the time and beeps the moment something burns, while it's still a small problem. Continuous testing watches every code change the same way.

Watch it happen

Tests on every push

Commit

Unit tests

Build

API tests

UI tests

Deploy

1/6A developer pushes code. The CI server starts the pipeline automatically.

The big ideas

What you need to know

Fast tests first

Order the pipeline from fastest to slowest so most failures show up in the first minutes.

The test pyramid

Many unit tests, fewer API tests, a small number of UI tests. UI tests are slow and brittle.

Flaky tests hurt trust

A test that fails randomly teaches people to ignore red builds. Fix or quarantine it quickly.

See it in code

Walk through the code

yaml

1name: tests2on: [push, pull_request]3jobs:4  test:5    runs-on: ubuntu-latest6    steps:7      - uses: actions/checkout@v48      - uses: actions/setup-node@v49        with: { node-version: 22 }10      - run: npm ci11      - run: npx playwright install --with-deps12      - run: npx playwright test

1/3Trigger: every push and every pull request.

A GitHub Actions workflow that runs Playwright tests on every push and pull request.

Save yourself the pain

Common mistakes

Oops

Putting hundreds of slow UI tests in the pipeline for every commit.

Do this instead

Run a fast core set on each commit and the full suite nightly.

Oops

Ignoring red builds because 'that test is always flaky'.

Do this instead

Fix or quarantine flaky tests. A pipeline nobody trusts gives no protection.

Your mission

Run tests on every push

~40 min

Quick check

Why do pipelines usually run unit tests before UI tests?

Go deeper

1Diagram where automated tests would run in a continuous testing pipeline (commit, build, deploy).
2Learn why continuous testing requires a strong automation foundation (Phases 6-7) to be practical.
3Preview Phase 11 for the CI/CD-specific mechanics of implementing this.