What is Shift Left Testing?

A picture is worth a thousand words. Here are how Shift Left differs from the traditional approach

How does my team shift left?

We started with unit testing, by developers, for their own codes. This is the easiest shift to implement, though it still takes time, effort, and patience to get it right. I recommend Pragmatic Unit Testing in Java 8 with JUnit if you want quickly level-up

The next step is to submit our codes to static analysis tests such as Sonar and Veracode.

We plan to further shift left by adopting Behavior-Driven Development and involving our QA colleagues as early as the design stage. This is a challenging approach because it involves multiple groups of people with different skills and preferences. We’ll need to find a consensus among them, appropriate attitudes, and the right skillsets to get it working. I figure once we deliver the first success, the rest will follow more naturally.

Reference

Shift Left to Test Fast and Reliably

My first introduction to Shift Left testing, documenting the real transition to the Shift Left model during the migration of Microsoft Team Foundation Server (TFS) to the Software-as-a-Service (SaaS) model

Shift Left Testing: What, Why & How To Shift Left

A good overview of what is Shift Left and how it differs from the traditional approach