1. SHIFT LEFT IN AUTOMATION
Taking a Step Ahead in Testing
Anil Jain,
Manager, Quality Assurance Engineering

2. Abstract Fast paced market expect reduction in project timelines
Late inclusion of automation in SDLC increases risk.
Automation strategy requires change in direction.
Guideline for making automation a success
This white paper covers ‘benefits’ and ‘things to consider’ before applying SHIFT LEFT in AUTOMATION.

3. Problem Statement

4. Delayed or Squeezed Testing Cycle

5. Delayed Realization of Benefits
Cost ( in %)
Time (in weeks)
NOTE: This is extrapolated data for one of in-house project.

6. Suggested Approach

7. Shift Left In Automation………..To Be Cont.

8. Guidelines to shift left in automation………..To Be Cont.
Collaboration with development team
Common Architectural & functional reviews
Use the same tools
Development Tool
Architectural Review
Collaboration

9. Isolate framework from Dynamic contents
Shift Left In Automation
Shift Left in Automation
Requirement
Design
Implementation
Testing
Maintenance
Automation Framework
Architecture
Functional Flow
Framework Logic
Dynamic Contents
Isolate framework from Dynamic contents
UX Design (HTML Source Code)
Application logic
Application Resource File
Data Base Design & StoredProcs
Developer
Automation Tester
Application
Automation Scripts

10. Test Planning for Shift left

11. Proof Of Concept       Testing with traditional approach
Problem Statement –
Reduce testing time for new biller module implementation for a Bill Payment system with same number of resources
Role
Time (days)
Remarks
Development 10
Developer – 4,
Architect - 1
Testing 8
Tester – 3,
Business Analyst - 1
Packaging & Deployment 2 
Project Duration – 18 days 
Team Size – 9 
Allow Shift Lift in Automation
Project Duration – 13 days
Role
Time (days)
Remarks
Development 8
Developer – 4,
Architect - 1
Testing 5
Tester – 3,
Business Analyst - 1
Packaging & Deployment 2
Team Size – 9 
Benefits –
Early defect detection
Time Reduction – 28 %
Effective and better Utilization of team members
Better cooperation & collaboration between teams
Better product understanding for testers by doing interaction with project binaries  

12. Benefit of Approach

13. Benefits of Shift Left in Automation
Cost savings by early defect detection
Early time to Market
Early Realization of Cost
Better Test Data Management
Promote testing and collaboration within project teams
Better product understanding for testers

14. Facts to consider ...
Benefits may be observed only on sizable projects
Benefits are widely observed on projects following Waterfall. For other projects benefits may not be significantly noticeable.
May cause rework in absence of collaboration and coordination

15. References & Appendix http://www.pnsqc.org/ http://www.satisfice.com

16. Author Biography – Anil Jain
Overall Experience: 11+ Years. (8+ Yrs. with Fiserv)
Current Role: Manager, Quality Assurance Engineering
Tools: UFT, Selenium, Coded UI, SOAP Sonar, SOAP UI, Appscan
Expertise: Designed multiple automation solutions and strategies for Web, windows and web services applications.

17. Questions & Answers

18. Thank you !!!