Automate All or Automation Smart

Transcript

1. Automation Testing V 1.0 Presenter: Biplab Chakraborty Date: 2024/01/17 Walking the line of smart testing
2. CONTENTS 1. Self Introduction 2. The Allure of Automation Everything 3. Understanding 'Automate Smart’ 4. The Risks of Over-Automation 5. Choosing What to Automate 6. Question
3. Self Introduction Personal and Professional Background: Born in India Graduated from University in India Started Career in 2011 Extensive experience in Software Testing from companies like: Rakuten, Cognizant, PwC, EY and Syntel Coding and food are passion Love to learn Japanese Love to indulge in quality time with Family
4. The Allure of Automation Everything
5. The Allure of Automation Everything Chronology Year 2011: There was a sudden escalation happened due to some defect leakages Director of Testing had meeting with Client Client was in anguish Test lead made promise of increasing the coverage Test Director makes promises of automation of all functional test cases And client understood , on a button click there will be whoooo..
6. The Allure of Automation Everything Choosing ‘bad’ candidates of automation: Test cases having dependencies with time. (For example : Receiving acknowledgement after 30 minutes) Rarely used test case Superficial UI Validation Highly complex less priority test cases Non feasible test cases
7. The Allure of Automation Everything What was the consequence: Higher failure rates Interrupted Execution Manual Intervention Reduced ROI Losing the trust from Test Automation
8. The Allure of Automation Everything Don’t use a canon to kill a fly
9. Understanding Automation Smart Agile Test Pyramid
10. Understanding Automation Smart Basic understanding on the application architecture Know how to read the developer console Cover the testing of API transactions in API testing Focusing more on Integration Testing (ex: CDCT for Microservice based architecture) Focus UI testing for UI Validation Create a few E2E flows Emphasize on Manual Exploratory Testing Collaboration with Developers
11. The Risk of Over Automation Maintenance Overhead Decreased flexibility Ignoring human insight Expensive set up process High Volume , higher risk
12. Choosing what to automate Repetitive Tasks Stable Features/Cases Complex and High priority functionality High risk areas
13. Take away "Don't Automate Chaos": Many times there will situations where automation will be suggested in peer pressure or from management which might be irrelevant. Need to be extra careful about that "Robots Don't Do Magic": All we are doing is creating some logic which automates the tasks . It’s better not to expect something phenomenal. It will only do things we have asked to do. "Beware of the Automation Zombie Apocalypse": Over automation might sometimes get you a good appraisal. But later this might come to you as Frankenstein.