The 911 system glitch has not just been a malfunction but a catastrophe to remember. It happened in Seattle in 2015 when the systems went down and it resulted in a national outage caused due to too much traffic on the number. Recently an incident occurred in Anderson County\u2019s communication center when a call came in and the dispatcher started typing notes for recording an incident. It could have been a medical emergency, house fire, or a theft. As the information was sent to paramedics, firefighters or Anderson County Sheriff\u2019s Office deputies; the system froze and computer screens stopped operating due to an unforeseen software glitch.<\/p>\n
Software glitches can not only cause damage to the brands, economic activity, and government organizations, but also lead to serious damage to the safety and well-being of human life. Disruption in the services provided by the county\u2019s computer-aided dispatch system can be disastrous, as every second counts.<\/p>\n
Marc Andreessen\u2019s article in the WSJ in 2011 \u2018Why Software is killing the World\u2019 is definitely a piece to remember, but today it\u2019s time to have an alternate perspective: \u2018How to save your software from being killed by a bug?\u2019 Testing early, and frequently is the solution. <\/strong><\/p>\n While early testing has been highly recommended by software testing and QA experts, there has been a special emphasis on this agile approach of Shift Left testing that recommends reversing the testing approach and involving system\/software testing earlier in the lifecycle. Practically, move the testing approach on the left end on the project timeline.<\/p>\n In an Agile development scenario, it is required to deliver faster and cut down the span of the delivery cycle. In a scenario such as this, it is absolutely critical to ensure the quality of the release while delivering at speed. It also implies that along with testers and their varying skillsets, the testing process will also involve the developers, where software testing will begin way ahead in the development cycle. This movement is referred to as shifting-left, and has become a preferred approach by many enterprises for better and faster results.<\/p>\n There are various stages that need to get covered in the software testing process \u2013 Test Requirement Analysis, Test Planning, Test Design, Test Execution, and Test Reporting. Every stage has its inherent benefits and contributes towards the testing activity. With the Shift Left approach, these activities start way ahead in the development cycle.<\/p>\n Let\u2019s understand the impact of Shift Left on the various stages in the software testing cycle.<\/p>\n Application of Shift Left approach reverses and speeds up the testing process, where there is more collaboration between Testing and Development, and the automation data can be gathered in the earlier phases of the Test Life Cycle. It further enables teams to detect bottlenecks early, reduce development costs, and improve time-to-market for products. It offers a stable and robust methodology to test unstable builds, where teams can also employ accelerators such as cloud-based load generation for both performance engineering and performance testing processes.<\/p>\n The Shift Left testing strategy emphasizes on the aspect of involving testing as early as possible in the development process. This enables both testers and development with diverse skill sets to unanimously focus on quality from day one of the project, instead of uncovering defects later in the development lifecycle. However, it can be a phenomenal task to make this possible and might involve shifts in team dynamics.<\/p>\n This agile testing approach shifts the entire testing process way earlier in the development cycle, which was traditionally placed at the end of the process. This implies that testers and developers collaborate and perform tasks which might not even be their primary responsibility. While Shift Left works to resolve bugs and issues on an ongoing basis, it is important to ensure that it is effectively implemented and enabled.<\/p>\n Here are some key principles to consider while enabling the Shift-left strategy.<\/p>\n The fundamental premise of Shift Left is to bring in more collaboration between testing and development. So, it is important that the entire responsibility of ensuring quality doesn\u2019t fall only with the testing team. It should be shared; which means that developers might assume the role of testers, and testers learn coding and take on the role of developers in the development cycle.<\/p>\n In a Test Automation scenario it is important to create reusable, maintainable code. Hence, another school of thought also recommends to shift this task to the developers and let them build the automation framework. This enables the testers to focus on finding bugs and not get deviated into programming the framework.<\/p>\n Testing and quality can be achieved only with team effort, irrespective of the role. It cannot be an activity conducted towards the end of the sprint. It has to be a unified effort that blends with development. Automation is an enabler for teams who have decided to dive into early testing. Early automation helps teams to cut down the testing efforts and detect bugs early in the cycle. Whether it\u2019s a developer or a tester, testing and quality has to be a constant thought. This will help teams to identify issues that can cause unreliable tests in case of loopholes in application testability code design.<\/p>\n A software glitch can result in a plane crash, a significant disruption of the economy, a major data breach or a cyber-attack. The year 2016-17 has witnessed some major setbacks and turmoil in the cyber world. We know that cyber war and attacks will not stop, but adoption of early and frequent testing can help identify gaps in the software and build more resilience. Shift Left testing approach enables the Agile methodology, which has been increasingly adopted by global enterprises.<\/p>\nHow Does Shift Left Testing Approach Enable Software Development Life Cycle?<\/h2>\n
\n
Why is it Critical to Effectively Enable a Shift Left Approach?<\/h2>\n
\n
\n
\n
In Conclusion<\/h2>\n