What does 'shift-left testing' mean in a CI/CD context?

In a traditional pipeline, QA runs after development finishes. Shift-left moves testing into the developer's workflow: unit tests run on save, API contract tests run on every PR, and linters and SAST scanners run before merge.

In CI/CD terms, shift-left means populating the earliest pipeline stages — commit, PR, merge — with fast, targeted checks, and reserving slow end-to-end suites for later stages or nightly runs. This keeps the PR build under 10 minutes while still catching most regressions early.

QA's role shifts from gate-keeper to enabler: writing tests that developers can run locally, defining the standards for the fast-feedback stage, and ensuring the pipeline fails on real quality signals rather than noise.