Shift Left and Shift Right concept in Software testing
Posted By : Manish Kumar | 28-Dec-2017
Talking about a decade above when testing was taken as a separate phase and considered that this phase starts at the end of software development. A similar scenario can also be seen in the Waterfall model.
Following waterfall model, testing phase appears in the last stage when all requirement, design, and coding phases are over. Which results in a huge loss of resource time and money as defects found in this stage will need more time to fix than a scenario if testing personal involved in the earlier stages.
Also, including testing at the earlier stages overcomes many of the bugs which occur due to wrong or missing requirements and wrong design
Visually it can be seen as :
As the above diagram shows cost of fixing a bug is increased significantly as the phases/stage increases.
Though to handle all these issues we have moved to V-model of software development in which testing phase is started along with the requirement collection only and also most important Agile model in which project only is made in the sprints and tested each and every phase for every type of issues.
It is also very much important to mention that applying a continuous and strenuous testing Work-force on the project that project is very much stable but its look is not of so much quality and Usability is not so much attractive to users, even then project owner may lose many of its target audience. Because only those project stands in the market which not only fulfills the user requirement but also its looks and usability attracts a user to use it again.
Left - Shift Testing Approach: As its name suggests we need to shift testing approaches at the earlier stages, unlikely as we have done in Waterfall model that Testing after the completion of coding phase, this will also help development team to change in their development modules early based on feedbacks and change reported, we need to start testing from the first phase as given below
1. Requirement Collection: in this phase Testing team will analyze the requirements and report for all type of missing requirements and Conflictions
2. Design: This time testing team will check for all navigational and transactional steps whether client requirements are fulfilled or not
3. Coding: This time testing team will check project thoroughly module by module.
Right - shift Testing Approach: Even after successful implementation and deployment of a project testing team must check the project continuously for the performance and Usability flaws under the real environment. Analyzing and working on the feedback from the target audience and giving a full satisfactory application to use is the only motto of testing
And after all, a project is stable, Automating the testing and Scaling of the project is left which are included in right shift testing approach.
Thanks
Request for Proposal
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
Manish Kumar
Manish is Adaptive and passionate to learn new technical skills, have knowledge of testing and love to play badminton in free time