Why Shift Left approach is necessary
Posted By : shruti gupta | 08-Jun-2016
Survey suggest that the cost of fixing a bug increases as a project move towards next stages in software development life cycle (SDLC). Detecting a bug early and fixing it immediately does not cost much. But if detecting it later or after production release, the result can be disastrous.
Due to this reason shift left approach is introduced.
In Shift left testing, testing is shifted towards left in SDLC (software development lifecycle), rather than testing at the end of the lifecycle.This approach allows developers to pay attention on quality right from the starting rather than waiting for bugs to be discovered late in the development life cycle.
Generally testing is done when development is in the coding phase that means testing is aimed at incorrect phase of development which might be neglecting many of the defects. Many defects occur during the requirement phase than during the coding phase of the project.
Using shift-left approach, it results in the following benefits:
- Bugs are detected and fixed early.
- Saving time and resources
- Better team work between developers and testers
- Cost effectiveness
Thanks
Cookies are important to the proper functioning of a site. To improve your experience, we use cookies to remember log-in details and provide secure log-in, collect statistics to optimize site functionality, and deliver content tailored to your interests. Click Agree and Proceed to accept cookies and go directly to the site or click on View Cookie Settings to see detailed descriptions of the types of cookies and choose whether to accept certain cookies while on the site.
About Author
shruti gupta
Shruti is a very sharp QA engineer with skills in manual testing of web and mobile applications. She loves to play chess and vollyball.