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

Shift-Left Testing

Part of the QA Testing Roadmap

In short

The earlier a bug is caught, the cheaper it is to fix. Shift-left means moving testing activities earlier in the timeline, toward requirements and design.

Moving testing activities earlier in the development process — reviewing requirements, writing test cases before code is even written — catching issues when they're cheapest to fix.

The purple blob at a railway booking counter carefully checks a ticket before leaving the window.

Think of it like this

Checking the name on your train ticket

Spot a spelling mistake in your name while booking, and you fix it in a second. Spot it when the TTE checks your ID on the train, and you're in real trouble. Shift-left is checking at booking time.

Watch it happen

Where the same bug can be caught

Requirements
0
Design
1
Code
2
Test
3
Production
4

1/5Found in production: users are affected, a hotfix is rushed, data may need repair.

The big ideas

What you need to know

Review before build

QA reviews requirements and designs and asks about edge cases before coding begins.

Developers test more

Unit tests, static analysis and code review catch bugs right where they're made.

Test APIs early

API tests can run before the UI exists, giving feedback days earlier.

Shift-right complements it

Monitoring and testing in production catch what's left. Many teams do both.

Save yourself the pain

Common mistakes

Oops

Thinking shift-left means QA does less testing at the end.

Do this instead

You still test the built feature. You just add earlier checks so fewer bugs reach that point.

Oops

Expecting shift-left to happen without developer buy-in.

Do this instead

It's a team habit. Agree on reviews, unit tests and early test sharing together.

Your mission

Shift one bug left

~15 min

Quick check

Which activity is the best example of shift-left testing?

Go deeper

  1. 1Identify a testing activity that could move earlier in a hypothetical project's timeline.
  2. 2Learn why fixing an issue found during requirements review is far cheaper than fixing it post-release.
  3. 3Preview Phase 10's Application Security connection to shift-left thinking in a security context.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge