Brace yourself from automation death trap
- 1. Brace yourself from the Automation Trap Prasad Kalgutkar
- 5. Save Time & Money Perform Exploratory Testing Analyze future requirements Deliver on time
- 6. Then why we fail?
- 7. Too much of unwanted automation Source: http://www.energizers.com/portfolio-
- 8. Automation done Perfunctory! Damn! We have agreed to automate, let me write some tests
- 9. “Are we building it correctly?”
- 10. My journey of challenges
- 11. eCom merce Train Travel Airline Travel
- 12. Airline domain with a big Enterprise Org Structure Mobile App Development & Frequent Releases Mixed Skilled Testing Team Distributed team across 4 locations
- 13. As a Agile QA, What it meant to me?
- 14. … automation serving as a help & not an overhead!
- 15. Some food for thought!
- 16. #1 Let automation run in the blood!
- 17. Be thoughtful while automating Desig n & ToolsClean Coding How much? & Where to? Runs on CI QA Build from CI
- 18. # Break the silos in testing # Every QA, contributes to # Best when business refers your test-cases
- 19. Let’s Refactor! Fail Fast, Grow Right! Add, Delete , Merge ! Optimiz e as you procee d
- 20. #2 Aim for the Test Pyramid
- 21. Test Pyramid Manual / Exploratory Imp act Busines s Facing Tests Technolo gy Facing Tests Tim e Cos t Integrati on JavaScript Web Service U I Unit View Courtesy: Anand Bagmar-What is Agile Testing?
- 22. # Unit Tests For iOS, Android, MWeb code Devs own while doing TDD # Integration Tests Devs own while doing TDD # Functional Tests Focus only E2EQAs/Devs own it # GUI E2E Tests Focus on UI details QAs/Devs own it
- 23. #3 Strongly dependent on OOPs concepts
- 25. The right way... ●Has only required user services ●Knows about the Locators & Next Navigation! ●Delegates user actions to Driver ●Registered with Page Registry User Profile Informatio n Accounts History Transfers Apply Loan Account Balance Open Demat Home Page
- 27. The Driver, => Provides actions to Page Objects => May have setup methods => Takes care of Waits
- 28. Single Test Layer ⇒ Invokes single step implementation ⇒ Calls relevant Page Objects ⇒ Respective Our Eco- system
- 29. #4 Test Cases: Try Behavior Driven
- 30. How Cukes helped … => Scenarios are E2E only => Acted as the Framework => Everyone collaborates! Given a ... When I ... Then I ... Scenario : To test...
- 31. Do’s ●Build independent test scenarios grouped in functional chunks ●If not cukes, provide sensible names to the tests ●Avoid setups in test-cases layer
- 33. Keep it understanda ble Keep it close to domain Keep it simple
- 35. WhenI search for flight with |origin |destination |type | | BOM | DEL | One way| ThenI should get “13A” as “aisle” seat
- 37. When I enter “VISA” card details Def testCards { “VISA” => { “Num” => “400010004000” “Exp Month” => “10” “Exp Year” => “}, “AMEX” => { … … …
- 39. GivenI have a “delayed_multi_pax” PNR in my trips some_step_def_metho d(type){ myPnr = PnrFactory.getPnr(type ) . . .
- 40. Avoid data sheets or CSVs Leverage the tech stack Avoid data fetching from
- 42. B’coz, ●Drivers, Page Objects are core! ●As the project grows, so do the contributors! ●When automation is the backbone of project delivery
- 43. “Get them running…” Get Continuous Integration
- 44. “ …is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day… Each integration is verified by an automated build to detect integration errors as quickly as possible … “ -Martin Fowler, ThoughtWorks Chief Scientist http://www.thoughtworks.com/continuous-integration Continuous Integration
- 45. “Every experience, no matter how bad it seems… Holds a blessing of some kind” - Gautam Buddha
- 46. Thank You