What is Shift – Left Testing?
It is an approach where the QA gets involved in the software cycle in the earlier stages to enhance efficiency and user experience and reduce cost.
Larry Smith coined the term “Shift-Left testing” in 2001.
Two Kinds of Shift Testing
o Shift Left Testing
o Shift Right Testing.
Comparison between Shift – Left testing and Shit – Right testing
·TDD (Test Driven Development) for Shift – Left testing
o QA starts writing test cases for the feature before coding starts.
o Developers code the feature.
o Testing and development continue till the feature passes the test cases.
o Then code refactoring is done to optimize, simplify, and improve maintainability.
Why is this a better process?
o A base is set before coding starts.
o Every code has the aim to pass the test and achieve the functionality.
o Test cases stay as a reference during coding.
o Collaboration between development and QA is strong to meet the required target.
o “Prevention over treatment” is followed.
Benefits for QA
o Improved product knowledge.
o Enhanced communication with the development and product team.
Challenges faced
o Need extensive planning and time management in every stage of the development cycle.
o The team needs to be well-versed in the feature to be implemented and understand how changes in the requirements can affect the product.
o The cultural reset of the organization should be positive and there should be no gap between the teams involved to ensure a seamless transition.
