Shift Left Testing (SLT)

Let's talk about the problem and its solution using the example of software development and the Shift Left Testing (SLT) method. According to research by the Rothman Consulting Group, the cost of fixing bugs after product release is on average 20 times higher than during full-scale multi-step testing during development. Logically, the concept of testing as a separate final stage of development seems unviable where quality needs to be ensured in a context with high development speed. As a result, Agile emerged as a counterbalance to the traditional (Waterfall) model.

The principles of it should have built the position of testing as a continuous process rather than a separate stage. However, the misunderstanding of Agile methodology often ends up only in the introduction of formal rituals and ceremonies, without qualitative changes from the inside. Once again, there is no panacea. Shift Left Testing (SLT) is remarkable as it requires revising the processes at the root, which you can't imitate with external attributes.

The idea of the approach is not new and once again states the well-known commonplace truth "Measure twice and cut once". The point is simple: start testing before the code is written. This way errors will be detected and corrected before they are actually digitized, which will significantly reduce financial costs and risks to the project and, therefore, speed up the process and improve the quality of the final product.

The SLT can be summarized literally in 6 points:

• Testing is an ongoing process, not a final part of the development
• Maximum quality assurance efforts should be focused on the first stages of development
• Testing of requirements allows you to remove most of the defects before their actual implementation
• Optimal results of development are achievable only with close cooperation of all participants of the project
• Use early introduction of automation
• The team is responsible for the result, and the project is in continuous improvement mode

The method, as an extension of Agile principles, can be interpreted in the traditional development model as well. Improving product quality and communication, speeding up the process, increasing product loyalty, increasing productivity seems to be the pluses of Shift left testing.

But will it affect the final cost of the project? Yes, the cost of development can increase at the stage of SLT implementation: early testing, new tools, high proportion of communication will inevitably entail additional costs. Costs where there were none before.

However, when considering an SLT implementation that focuses as much as possible on the early stages of development, it is worth remembering that its goal is to solve problems that arise at the very end of the process. Therefore, in the long run, you will definitely find significant savings on bug fixing.

Of course, claiming that Shift Left Testing is a cure for all ills is impossible, the benefits of SLT is directly dependent on the specific project and a number of factors, such as the size and maturity of the team, the complexity of the product, customer engagement and, of course, the desire to change something for the better. And the latter is probably the most important factor.