It’s reasonable to ask whether shifting testing left means that QA engineers will be out of job. Nothing could be further from the truth.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Shifting testing left empowers more developers to run and maintain tests, without eliminating the role of QA. QA becomes a strategic leader in defining testing strategy, maintaining automation, and optimizing test execution. Shifting left enhances development velocity, reduces bugs in production, and allows developers to verify their work immediately.

Why Shift Testing Left Part 2: QA Does More After Devs Run Tests

Conclusion: Shifting Left Is a Return to the Good Old Days

<p>The part this gets right that most shift-left writeups miss: QA’s job moves from running tests to owning the testing system - strategy, flake policy, what’s worth automating at all. The trap in practice: orgs shift the test-writing left but keep QA accountable for quality without authority over the process. If devs own the tests and QA owns the strategy, someone still has to own the flake budget - otherwise “more devs run tests” just means more unowned red builds.</p>
