Download to read offline
Uploaded byBas Dijkstra
Why do we automate?
This document discusses the importance of asking "why" when automating tests. It notes that while the focus is often on how to automate and what tools to use, asking why helps ensure the right tests are automated in the right way. Specifically, asking why helps manage expectations around automation, determine if a specific test is worth automating and if the method of automation is efficient. The document encourages collaboration between industry and academia by asking why each group does what it does. It concludes by asking the reader why they personally automate tests.
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Why do we automate?
- 1. Why do weautomate? Bas Dijkstra bas@ontestautomation.com www.ontestautomation.com @_basdijkstra Nederlandse Testdag 2018
- 2. My story until alltoo recently… @_basdijkstra
- 3.
- 4. Automate all thethings. @_basdijkstra End to end.
- 5.
- 6. “I’m sick andtired of repeating myself” -- History @_basdijkstra
- 7. Questions, questions… What toolor 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! @_basdijkstra (*) Should run on blockchain
- 8. Automation is everywhere… @_basdijkstra … but we need people that ask the right questions
- 9. There is no‘one size fits all’ in automation @_basdijkstra
- 10. At some pointin time, we forget to ask the important questions @_basdijkstra
- 11. WHY HOWWHAT> > @_basdijkstra Wefocus almost exclusively onWe focus far too little on
- 12. @_basdijkstra Create your ownHTML 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?
- 13.
- 14. What happens whenyou ask ‘why?’ a little more often? @_basdijkstra WHAT > HOWWHY >
- 15. Why automate inthe first place? Because we want to shorten feedback loops Because we want to focus on the complex, the interesting stuff Because we want to develop and test more efficiently @_basdijkstra Because … WHAT > HOWWHY >
- 16.
- 17. Why automate this specifictest? @_basdijkstra WHAT > HOWWHY >
- 18. “Are we comfortable withnot having the information provided by this test?” @_basdijkstra
- 19. Why automate this specifictest in this specific manner? @_basdijkstra WHAT > HOWWHY >
- 20. “Is this themost efficient way to get the information we’re looking for?” @_basdijkstra
- 21. Don’t just solvethe problem right. @_basdijkstra Solve the right problem, too.
- 22. And since we’rehere together… @_basdijkstra
- 23. For those inacademia Ask people in the industry ‘why?’ they do things the way they do it Show them relevant research Ask for input @_basdijkstra
- 24. For those inindustry Ask people in academia ‘why?’ they do the research they’re doing Show them industry problems Collaborate @_basdijkstra
- 25.
- 26. Why do YOUautomate? @_basdijkstra
- 27. Get in touch! _Email:bas@ontestautomation.com _Blog: https://www.ontestautomation.com _LinkedIn: https://www.linkedin.com/in/basdijkstra _Twitter: @_basdijkstra
Editor's Notes
- #3 In the first 8 years of my career I wrote an awful lot of horrible automation
- #4 This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #5 This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #6 Example Orange
- #7 This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #8 Saving money > discuss ROI NEEDS REWORK
- #9 This was basically my motto (use example from Orange) – metrics: number of regression tests automated
- #10 What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #11 What works in a specific situation, in a specific context, is not guaranteed to work somewhere else
- #12 Part of the problem is people not asking the right questions, it’s all about the how, how, how…
- #13 Do we really want more of those test automation engineers?
- #14 As a result, we end with a lot of horribly inefficient automation that’s hard to maintain
- #16 Saving money > discuss ROI NEEDS REWORK
- #17 Asking ‘why?’ helps to manage expectations
- #23 I think this applies to both academics and industry
- #24 Saving money > discuss ROI NEEDS REWORK
- #25 Saving money > discuss ROI NEEDS REWORK
- #26 I think this applies to both academics and industry
- #27 What works in a specific situation, in a specific context, is not guaranteed to work somewhere else