20190919 backbase why_do_we_automate
Download as PPTX, PDF1 like92 views
This document discusses why automation is important and encourages asking "why" more often to ensure the most efficient approach. It suggests automating tests specifically to get necessary information before deployment and in the most effective way. The document also advocates understanding the problem before choosing tools or languages and managing expectations around what can and cannot be automated.
20190919 backbase why_do_we_automate
- 1. Why do we automate? Bas Dijkstra bas@ontestautomation.com www.ontestautomation.com
- 2. My story until all too recently…
- 4. Automate all the things. End to end.
- 6. “I’m sick and tired of repeating myself” -- History
- 7. Questions, questions… What tool or language do I need to learn? How can I automate action ABC with tool XYZ? How can I retry my tests automatically? I want to create a keyword-data-driven hybrid multiplatform AI-powered test framework(*), help me! (*) Should run on blockchain
- 8. There is no ‘one size fits all’ in automation
- 9. WHY HOWWHAT> > We focus almost exclusively onWe focus far too little on
- 10. Create your own HTML report from Selenium tests FindBy strategies for Selenium explained Data driven testing in Selenium Webdriver using Excel 2014 2015 2013 14080 12037 10011 Stop sweeping your failing tests under the RUG Trust automation On asking ‘why?’ in test automation 2017 2017 2016 365 774 470 HOW? WHY?
- 11. Result!?
- 12. Automation is everywhere … … but we need people to ask the right questions
- 13. Ask ‘why?’ a little more often WHAT > HOWWHY >
- 14. Why automate in the first place? WHAT > HOWWHY >
- 16. @_basdijkstra
- 17. Why automate this specific test? WHAT > HOWWHY >
- 18. “Are we comfortable with not having the information provided by this test?”
- 19. “Are we comfortable with not having the information provided by this test before we deploy?”
- 21. Why automate this specific test in this specific manner? WHAT > HOWWHY >
- 22. “Is this the most efficient way to get the information we’re looking for?”
- 26. CV – T.A. Tester Tools Selenium WebDriver (4.9 years) JMeter (3.2 years) Cypress (0.2 years) … Recent projects Finance (2018 – now) Built framework in Java Selenium WebDriver from scratch Used Jira … Utilities (2016-2018) Built framework in Java Selenium WebDriver from scratch Applied dependency injection using Google Guice …
- 28. Awesomely hot job opening Software Developer in Test (SDET!!) Amsterdam, full time, permanent The ideal candidate has • Built frameworks from scratch before • 10+ years of experience • Mad skills with Selenium (knockout!) • Mad skills with Cucumber (knockout!) • Mad skills with SpecFlow (knockout!) • Mad skills with Jenkins (knockout!) • Mad skills with Knockout (knockout!) • …
- 30. So, instead of… We need someone to automate all of our… Can I use tool XYZ to do… How close are we to 100% automated coverage of… What language do I need to learn to…
- 32. Why do YOU automate?
- 33. Get in touch! _Email: bas@ontestautomation.com _Website: https://www.ontestautomation.com/training _LinkedIn: https://www.linkedin.com/in/basdijkstra
Editor's Notes
- #3: In the first 8 years of my career I wrote an awful lot of horrible automation
- #4: Example Orange
- #5: This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #6: This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #7: This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #8: Saving money > discuss ROI NEEDS REWORK
- #9: What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #10: Part of the problem is people not asking the right questions, it’s all about the how, how, how…
- #11: Do we really want more of those test automation engineers?
- #12: As a result, we end with a lot of horribly inefficient automation that’s hard to maintain
- #13: This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #15: Saving money > discuss ROI NEEDS REWORK
- #16: Asking ‘why?’ helps to manage expectations
- #17: Example Orange
- #27: A typical job opening
- #28: What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #29: A typical job opening
- #30: What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #31: Saving money > discuss ROI NEEDS REWORK
- #32: What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #33: What works in a specific situation, in a specific context, is not guaranteed to work somewhere else