Software Testing - Strategy being redefined : Shift Left Strategy.

1. Software Testing UnPlugged
Raghava Balaji

2. Software Testing - Paradigm Shift
•The whole approach to software testing is undergoing a sea change
•With emphasis on reducing the “Cost of Quality” and with increasing Pressure on “Time to
Market” testing strategy is being redefined
•“Shift Left Strategy” is the new mantra and the whole focus is now on unearthing business critical
defects in the early phase of life cycle – result Impact on Cost & Quality

3. Software Testing - Paradigm Shift
Requirements Phase
•Domain Experts / Subject Matter Experts (SME’s) part of the testing team are now being involved
during the “Analysis Phase”
•SME’s work closely with Business Analysts and thoroughly analyze the “Business Requirements”
•Intent is to ensure that there are
•No Ambiguous Requirements
•Capture Requirement Defects upfront
•Capture Requirement Gaps
•Capturing the “Requirement Gaps / Defects” before the coding saves not only cost but also time –
“Cost of Rework” increases as defects are found later in the life cycle

4. Software Testing - Paradigm Shift
Design Phase
•Test Cases should be designed from the business perspective covering End to End business
scenarios
oEffective test case design helps unearth requirement / design defects
•Automating the test case creation is gaining momentum – Saves time and enhances coverage
•While designing test cases it should be ensured that the test cases are assigned the right priority –
from business stand point
•Once the right priority is assigned building a robust regression suite becomes easier with high
priority test cases and some of the medium priority becoming part of the regression suite
•During Crunch time lines identifying the high priority test cases becomes easier for execution

5. Software Testing - Paradigm Shift
Execution Phase
•Integrated SIT / UAT approach to execution is gaining momentum
•Execution should not just be from functional stand point but also cover End to End flow
•Resorting to Priority Based approach ensures that the high priority business scenarios are
covered with high priority defects detected early in the execution cycle
•Identifying the defects during early execution cycle gives development team time to fix the
defects and also increases the confidence on the release
•Automation coupled with Priority Based execution approach also saves time

6. Conclusion
To Summarize:
Early involvement of Testing Team
•SME’s Partnering with BA’s during Requirement Phase
•Possible Automation of Design Phase
•Integrated approach to execution coupled with automation & priority based testing
•Result
•Saves Time and Cost
•Faster Time to Market
•Enhanced Customer Satisfaction