4 P's of Introducing Agile Test Automation in Agile Way

Uploaded on

This is a case study about : …

This is a case study about :
1. Introducing Test Automation from scratch in a world of manual testing
2. Challenges in test automation for both legacy and new products
3. Realization cycle from Peril to Pleasure in introducing Agile Test Automation

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. 1
  • 2. 2 Pain, Peril, Pitfall, Pleasure – 4P From Nowhere to Somewhere
  • 3. 3 Iterations are continuous journeys. Make a Beginning
  • 4. Our World 4 Understanding the context of operation Consumers Business Needs Environment
  • 5. Our Goals 5 Engineering teams strived for… On Time Delivery Quality
  • 6. Our Structure 6 Understanding links in the chain Product Management (Bid, Pre-Sales, Sales) Product Units (Engineering) Product Validation Group Implementation Group CEG (Core Engineering Group) DPM (Delivery Program Management) Global Support Group CUSTOMER CUSTOMER
  • 7. Our Concerns 7 Hangover Lessons and Sleepless nights Delayed Deliveries Quality
  • 8. 8 Test Automation – Challenge
  • 9. The Opportunity 9 ‣ Heterogeneous Software ‣ Heterogeneous Environments ‣ Legacy Products ‣ Conditioned Minds (Not my problem or it is always done this way) ‣ Non productive labor ‣ Insecurity ‣ Unpredictable schedules ‣ Non-release mode ‣ Multiple Stakeholder ‣ Structural Complexities Every problem is an opportunity. Is there any other choice really ?
  • 10. 10 Running away was the only option but….
  • 11. 11 Persistence pays – The EMI of course!
  • 12. Our Journey… 12 ‣ Agility and rapid acceleration vs. Speed. ‣ Course Corrections and adapting to context during journey Cheetah way – Agile Hunter Source: New York Times
  • 13. Process and tools Individuals and interactions over Following a planResponding to change over Source: www.agilemanifesto.org Comprehensive documentation Working software over Contract negotiation Customer collaboration over Agile Manifesto Value Driven
  • 14. The Journey 14 Shifting Mindsets Pain Peril Pitfall Pleasure Oh My God ! Should we ? What the ? We did it
  • 15. There are no silver bullets 15 ‣ Examine the chain ‣ Look at Data ‣ Anti-pattern on theory of constraints ‣ Crawl, Walk , Run ‣ Are we doing the right thing? The chain is as strong as it’s weakest link. But what is the chain is only made of weak links
  • 16. Our Structure 16 Critical links in the chain Product Management (Bid, Pre-Sales, Sales) Product Units (Engineering) Product Validation Group Implementation Group CEG (Core Engineering Group) DPM (Delivery Program Management) Global Support Group CUSTOMER CUSTOMER
  • 17. Quality and Efforts 17 Software Testing and its value to different stake holders For Engineers To Customers GUI and System Tests (Validation Group) Functional Tests (Product Units) Unit Tests (Product Units) GUI Tests (High Access and Visibility) Functional Tests (Medium Visibility) Unit Tests (Low Visibility)
  • 18. No one size fits all 18 ‣ Staged Interventions ‣ Start with most pained soul(s) Understand local context
  • 19. Transformation is a journey. 19 ‣ Get stakeholder buy-in ‣ Agree upon terms of success ‣ BHAG into sprints ‣ Delay explaining the ‘How’ ‣ Nudge, Nudge and Nudge gently Rome was not built in a day
  • 20. Partner for tools and tailor 20 ‣ Getting out of DIY syndrome ‣ Go for lightweight tools and Adapt ‣ Cover Risks ‣ Win-Win Partner relationship Co-Create
  • 21. Where to Begin ? 21 Multiple Challenges for Adoption
  • 22. Tools Evaluation 22 Evaluated different tools for Web Test Automation.. Feature Selenium Sahi OS (Open Source) Sahi Pro QTP Jameleon TestingAnywh ere Watir Developed into Java Java Java .Net Java Java Ruby Record and Play Only on Firefox All browsers All browsers Only on IE No Yes No Playback Yes Yes Yes Yes Yes Yes Yes Brower support All All All IE IE All All OS/Platform support All All All Windows Windows All All Language Multiple Javascript, Java, Ruby Javascript, Java, Ruby VB XML Java,.Net,C++Ruby Usability Easy Easy Easy Easy Easy Easy Easy Automation/Maint enance difficulty level Easy Easy Easy Easy Easy Easy Easy Exception handling Yes Yes. Has recovery feature & Call back function. Yes. Has recovery feature & Call back function. Yes Yes Yes Yes Parallel Testing Yes Yes Yes No No Yes Yes
  • 23. Get Along - Partnership 23 Chosen Partnerships “make” vs. “buy” SAHI Pro Automation Framework
  • 24. Collaborate to succeed 24 ‣ From ‘They’ to ‘We’ ‣ Demonstrate end to end ownership ‣ Take People Along ‣ Empathetic Listening Seek to understand
  • 25. Customer Collaboration 25 Validation Group Product Units Core Engineering Group Product Management -Identify and Share most painful solution under test -Define and agree to success criteria of resolution -Automate the identified cases -Show value to both validation and engineering Units -Nudge engineering units for adoption
  • 26. Do not be afraid to fail 26 ‣ Results not as expected ‣ Not walking the ‘Talk’ ‣ Violation of ‘What we Preach’ ‣ Slipped Commitments ‣ Eat your dog food Recover Fast
  • 27. Sprints Progress 27 Automation of Tests… Sprint # Planned Scenarios Accomplished Scenarios First 500 110 Second 350 391 Third 250 245 Fourth 300 310 Total 1400 1056
  • 28. Persistence shall trump talent 28 ‣ Negative Sentiments ‣ Self Doubt ‣ No Acknowledgements ‣ This too shall pass Hang in there
  • 29. Shift in Mindset 29 ‣ Resistance to Change – Hierarchical Structure ‣ Frustration to Discipline ‣ Transparency and Accountability ‣ Closed Communication to Openness ‣ Individual Performance to Team Performance Cultural and Behavioral Changes in the Teams
  • 30. Advertise success 30 ‣ Start Hallway talks ‣ Do the elevator pitches ‣ Publish results ‣ Tickle the curiosity ‣ Informal evangelization Celebrate Wins
  • 31. Success Stories Published.. 31 Savings of efforts on Testing – On Time and With Quality Unit Solution Test Scenarios Manual Execution Automation Execution Savings Unit-1 P1 1500 40.5 Person Days 15 Hours 95% Unit-2 P2 230 7 Person Days 1 Hour 15 Minutes 97% Unit-3 P3 142 4 Person Days 40 Minutes 96% Unit-4 P4 119 3 Person Days 7 Minutes 99% Unit-5 P5 25 1 Person Day 2 Minutes 99%
  • 32. Advertisement 32 ‣ Internal Communication ‣ Technical talks and formal discussions Different modes to publish the success stories
  • 33. Identify early adopters 33 ‣ Degree of Bias ‣ Incubate your people into their teams ‣ Accelerate their adoption Help them spread the word
  • 34. Get them hooked 34 ‣ Go backstage ‣ Evolve and feed continuously ‣ They become your champions ‣ Move on. Go to the next link in the chain Get out of the way
  • 35. What’s Next ? 35 ‣ Continue to focus on “Agile Adoption” ‣ Scrum Adoption for other teams ‣ Continue “Automation” • Functional and Unit Tests – Unit Testing • Encourage, Promote and adopt Test Driven Development (TDD) • In house Framework development Still it is the journey…
  • 36. Recap 36 Iterate, Iterate, Iterate ‣ There are no silver bullets ‣ No one size fits all ‣ Transformation is a journey ‣ Partner for tools and tailor ‣ Collaborate to Succeed ‣ Do not be afraid to fail ‣ Persistence shall trump talent ‣ Advertise Success ‣ Identify Early Adopters ‣ Get them hooked
  • 37. 37
  • 38. 38 Secret Ingredient - Belief in Self
  • 39. 39 Have fun
  • 40. 40 Mahesh Ghatage Zunder Lekshmanan Thank you mahesh.ghatage@mahindracomviva.com zunder.l@mahindracomviva.com