Shift-Left Testing

                                                            SHIFT-LEFT TESTING


Shift lift testing is an approach to the software testing and system testing in which testing is performed earlier in the life cycle.
Firstly, the principle of ‘Shift left’ supports the Testing team to collaborate with all the stakeholders early in the software development phase. Hence they can clearly understand the requirements and design the test cases to help the software ‘Fail Fast’ and enable the team to fix all the failures at the earliest.
Shift Left approach is nothing but involving the testers much earlier in the software development life cycle, which in turn would allow them to understand the requirements, software design, architecture, coding and its functionality, ask tough questions to customers, business analysts, and developers, seek clarifications, and provide feedback wherever possible to support the team.

This involvement and understanding will lead the testers to gain complete knowledge about the product, think through various scenarios, design real-time scenarios based on the software behaviour which would help the team in identifying the defects even before coding is done.











Shift Lift Approach influences Software Development in several ways----


· Shift Left approach focuses on involving testers in all and most importantly the critical stages of the program.
· Shift Left approach gives the opportunity for the Testers to design the tests first,
· IT allows the Developers to take more ownership of their code and increase their responsibilities on testing.
· Shift Left approach also encourages testers to adopt Behavioural Driven development and Test driven Development.
· Shift Left Testing in Agile: Shift Left approach supports forming Agile Scrum Teams which mandatorily includes Testers along with the other roles and includes Testers in regular stand up calls, other interactions, review meetings which has made the testers to have more information related to the program and hence has allowed them to indulge and involve in the detailed analysis of the software and provide rapid feedback which would help in preventing the defects grounded in the software.