From quality assurance to quality engineering: Why you should use shift-left testing

If you work in the software industry, you’ve most likely heard about “shift-left testing” from conferences, blog posts, industry publications, co-workers, etc. With Agile practices (including TDD, BDD, and CI) and DevOps increasing in popularity, “shift-left” is the answer to how QA fits in, making them a reality in your organization rather than merely aspirations. Making this shift changes the view of testing- instead of traditional QA, it transforms into QE: Quality Engineering.

What is meant by Shift-Left Testing?

Shift-left testing refers to the integration of testing activities with development, beginning sooner in the development cycle, rather than later as in traditional software development environments like waterfall.

[tweet_box design=”box_01″ float=”none” excerpt=”A successful tester has to not only be great at testing, but an engineer of the Agile testing process.”]To be successful today, a tester has to not only be great at testing, but also be an engineer of the Agile testing process.[/tweet_box]

This means working together with development and operations and analyzing quality during every stage of development as shown in the graphic below.

Artboard 1-minFor example, testers have to jump in and take a more proactive role even before development starts by being present during the gathering of requirements.

Other activities include:

●  Testers helping developers implement unit testing
●  Planning, creating, and automating integration test cases
●  Plan, create, and employ virtualized services at every stage and component level
●  Gather, prioritize, and process feedback

Some process changes that occur during the shift may include the following:

●  Instead of waiting weeks to add code to that of the rest of the team, do it every day, or even several times a day.
●  Instead of manually performing all the tests, automate and run them every day, or even several times a day.
●  Instead of detecting problems at the end, analyze quality as the development progresses.

Why make the shift if you haven’t yet?

In this post, we’ll provide just three main benefits of shifting left: reduce costs, increase efficiency and quality, and gain a competitive edge.

shift-left testing benefits


It is still true what Larry Smith said over 15 years ago, when the “shift-left” concept was first introduced, “bugs are cheap when caught young.”

One of the aims of Agile testing is detecting errors as soon as possible. What we mean by as soon as possible is: as soon after the exact moment in which the error was inserted into the system.

When testing is done with every build (especially during unit testing), the errors that are found are smaller, easier to detect and locate, and also, less costly to fix. Assuring the quality as we go also means eliminating the tremendous costs and the unnecessary work of having to go back and re-do certain things.

For more information on how much money it saves, read this post on the ROI of test automation.


We often find that the increased levels of automation when shifting left allows for:

●  Increasing test coverage by running more tests in the same amount of time
●  Freeing up time for testers to focus on more challenging and rewarding tasks
●  Reducing human error
●  Monitoring performance over time
●  Code quality checks
●  Built-in security checks
●  Reducing issues in production (that users will face)

Beyond these benefits, being able to start testing sooner invariably results in more quality, as testers are not rushed to find all the errors at the end, only leaving whatever time is left to spare for them.


Shifting left your QA gives you a competitive edge in two ways: speed up time to market and attract top talent.

About staying competitive in today’s ever changing technological landscape, Alon Girmonsky, founder of BlazeMeter (acquired by CA Technologies), said it best:

[tweet_box design=”box_01″ float=”none” excerpt=”The only way to defend one’s stature is by innovating in short iterations via @AbstractaUS @alongir #Agile”]Today, the barrier to compete is minimal, and the only way to defend one’s stature is by innovating in short iterations… meaning adopting Agile.” – Alon Girmonsky[/tweet_box]

As we can all agree that it is important to deliver software more quickly, it also shouldn’t be rushed out the door. Shift-left testing answers the problem of accelerating development without sacrificing quality.

Secondly, shift-left testing is what software developers and test engineers expect today of their organization, officially becoming mainstream with over 66% of IT workers reportedly using Agile or “leaning towards Agile” methods.

In Zephyr’s latest report, “How the World Tests 2016,” the amount of respondents who use Agile/Scrum, Waterfall, or a hybrid of the two are shown in this diagram from its report:

Agile, Scrum, Hybrid, Waterfall diagramAnd, it’s not surprising that one of the key findings of the State of Software Testing Report 2015-2016, 55% of testers reported they were already doing or wanted to implement Continuous Testing and Continuous Integration.

Therefore, if you want to be an attractive employer or at least on-par with the rest, it is important to adopt the modern practices that both testers and developers want to master in order to stay relevant in today’s labor market.

When shift-left testing doesn’t work

Maybe you have heard all of those benefits already, but you are STILL not convinced about shift-left testing for this reason: you’ve seen that even Agile teams can face the same bottlenecks as seen in Waterfall.

For example, as Shridhar Mittal, former GM of Application Delivery at CA Technologies, explains, “Due to the complexity of environments and composite applications, Agile teams are often stuck waiting in a queue once all of the pieces come together in the performance and user acceptance testing phases.”

The solution he provides that we agree with is utilizing service virtualization. Service virtualization emulates the behavior of essential components that will be present in production, enabling integration tests to take place much earlier in development. This is how you can eliminate that key bottleneck, while also benefitting from eliminating errors earlier on.

Along with service virtualization, you have several tools to setup your automated systems and CI such as Jenkins, CruiseControl, Bamboo and TeamCity, which all have web management interfaces. Or, you could go with a cloud solution like Amazon Pipeline Code, TravisCI, CircleCI, Codeship and Microsoft’s Visual Studio Team Services.


Just having these tools in place does not ensure a successful shift and does not imply quality engineering. There are several preconditions, and a level of testing maturity that must be reached in order to achieve Continuous / Agile / shift-left testing. For example, a precondition for test automation would be having the appropriate test environments set up. Without this and several other preconditions, your shifting of QA to the left will be problematic, at the least.

Stay tuned for more content coming soon on how to lay the path towards Continuous Testing! Subscribe below to never miss a beat. 

Wrapping up

With Agile being the norm, shift-left testing is a key enabler for increasing quality and efficiency, reducing costs and risks, and staying competitive. In shift-left testing, everyone becomes a quality engineer and the responsibility for producing high quality software is equally shared among the team.

This ultimately results in a better product, shipped even faster.

Who wouldn’t want that?

Check out these related posts

Best Testing Practices for Agile Teams: The Automation Pyramid
The 4 Most Common Test Automation Challenges (and How to Overcome Them)