Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Check This - Test Automation, A Development Managers View

153 views

Published on

Test automation belongs to the testers and as testers we care about quality more than the rest of the development team do, right? It’s easy to think this. I know, I’ve been there, as a Tester and a Test Manager.

But now I manage the whole development team and can see how the whole team should use test automation. And how we could get more efficient as a team when we all became responsible for quality.

Published in: Software
  • Be the first to comment

Check This - Test Automation, A Development Managers View

  1. 1. Check This Test Automation A Development Managers View @stephenjanaway
  2. 2. HELLO! @stephenjanaway
  3. 3. Head Of Technology VP Engineering Senior Quality Gate Manager Tester Test Lead Developer (first job) Quality Gate Manager Delivery Manager ? Test Manager Test Manager Test Coach ? Why Should I Be Talking To You?
  4. 4. DISCLAIMER MY CONTEXT, MY PROBLEMS, WHAT I’VE SEEN WORK
  5. 5. Test Automation At a Leading Fashion E-commerce Company @stephenjanawayLicensed under Creative Commons Attribution 2.5 Denmark. - Benjamin Suomela/norden.org
  6. 6. You aren’t there to make the automated tests pass @stephenjanaway
  7. 7. Photo: https://www.flickr.com/photos/cgrusden/ “Good testing involves balancing the need to mitigate risk against the risk of trying to gather too much information” Jerry Weinberg @stephenjanaway
  8. 8. Some Terminology @stephenjanaway
  9. 9. What Is Testing? Trying the software to see if it works... @stephenjanaway
  10. 10. Testing The process of evaluating a product by learning about it through exploration and experimentation Source: http://www.satisfice.com/blog/archives/856 @stephenjanaway
  11. 11. Checking The process of making evaluations by applying algorithmic decision rules to specific observations of a product Source: http://www.satisfice.com/blog/archives/856 @stephenjanaway
  12. 12. Test Automation Writing code to check, AND help testing @stephenjanaway
  13. 13. Team A group of awesome people who want to deliver value Your job as a manager is to enable them to do that @stephenjanaway
  14. 14. Now what? Train them Find the people What Is Automation anyway? Saving the world Start here Build a great team Get it live What should you care about? Choose a tool Let’s Go On a Journey Plan your project End here
  15. 15. Why Do We Need Test Automation Anyway? @stephenjanaway
  16. 16. Photo: https://www.flickr.com/photos/cgrusden/ “Done is better than perfect because something is better than nothing” Sheryl Sandberg
 @stephenjanaway
  17. 17. “People who don’t really get testing tend to want to turn it into a programming problem instead” Jeff Nyman @stephenjanaway
  18. 18. What Should a Manager Care About? " Predictable, efficient software delivery " A happy, motivated team " Easy (as possible) hiring of new people " A team that cares about quality @stephenjanaway
  19. 19. Your Test Automation Won’t Save The World " It’s tempting to eat the “Selenium” donut " But is it short term pleasure? " Automation is not rocket science, but it’s not trivial either @stephenjanaway
  20. 20. Recognise That Test Automation Doesn’t Just Mean Writing Checking Code " The ickle test helper " Testing tools save time and promote efficiency " This is automation in testing @stephenjanaway
  21. 21. “Automation is the judicious application of technology to help humans do their jobs” Paul Grizzaffi @pgrizzaffi @stephenjanaway
  22. 22. Ringelmann Effect @stephenjanaway “The tendency for individual members of a group to become increasingly less productive as the size of their group increases”
  23. 23. You Don’t Need a Test Automation Team " Silo’s breed apathy " Testers should be in teams " Pairing with developers - building a bridge " Team’s own quality " A separate test automation team is a lonely place @stephenjanaway
  24. 24. Team’s Own Automation UI Tests API Contract Tests Unit Tests Web & Mobile Clients Platform {Team @stephenjanaway
  25. 25. Automate (a lot) of the things as a team @stephenjanaway
  26. 26. @stephenjanaway
  27. 27. Orders of Ignorance @stephenjanaway
  28. 28. 3rd Order Ignorance: Lack of Process I don't know a suitably efficient way to find out I don't know that I don't know something 2nd Order Ignorance: Lack of Awareness I don't know that I don't know something 1st Order Ignorance: Lack of Knowledge I don't know something 0th Order Ignorance: Lack of Ignorance I (probably) know something Good Testing @stephenjanaway
  29. 29. Automation Can Do a Lot But It Can’t Check... Thought patterns User reactions Usability Perceived Performance Claims Unknown behaviours What If I…? Look and feel Accessibility Compatibility @stephenjanaway Ambiguity Business understanding Value judgements Do you need more tests?
  30. 30. Automation Can't Check All Of This... Thought patterns User reactions Usability Perceived Performance Claims Unknown behaviours What If I…? Look and feel Accessibility Compatibility @stephenjanaway Ambiguity Business understanding Value judgements Do you need more You Can Only Automate What You Know and Expect 2nd Order Ignorance: Lack of Awareness I don't know that I don't know something
  31. 31. You Need Exploratory Testers " Tools cannot reason " Tools will not look for ambiguity " Tools do not understand your business " Tools will not make any value judgments about tests " Tools don’t know how to produce further tests @stephenjanaway
  32. 32. If You Must Hire Test Automators Then Do So With Care " When you hire developers then talk to them about testing " Watch out for the developer foot in the door " Think about remit " Hire like you would hire a developer. Be technical. Have technical tests " Expect them to think like a developer " Expect them to think like a tester @stephenjanaway
  33. 33. If You Must, Train With Care " Don’t get your existing test automators to train your exploratory testers " Invest in your team and that means paying for training " If you are serious about test automation then be serious about the cost " Wouldn’t it be better to train the developers to be better testers? @stephenjanaway
  34. 34. No one would ask a developer to teach an employee to code from scratch Why Is This Acceptable For Test Automation? @stephenjanaway
  35. 35. Care About Flow " Predictable cycle times " Does my automation help? " When team’s own automation then work flows more smoothly @stephenjanaway
  36. 36. @stephenjanaway Design Develop Test Release Months Weeks Weeks Weeks Don’t ever do this (again)
  37. 37. Present Bias “The tendency to over-value immediate rewards at the expense of our long-term intentions” @stephenjanaway
  38. 38. Don’t Automate All The Things Lots of automated tests is not something to be proud of: " Who debugs the tests? " Who maintains the tests? " Can you efficiently scale the team to keep up? " How quickly do the tests generate results? Information? Value? Exploit Present Bias with Tea @stephenjanaway
  39. 39. Team Automation Establishes Common Ground " A shared language " Easier pairing " A bridge to build better relationships @stephenjanaway
  40. 40. Testing Tool Vendors Promise You The Earth Vendors and test centres make fancy and outlandish claims. " 100% test automation " Replace all your manual testers " 76% efficiency increase Be wary @stephenjanaway
  41. 41. Don’t Dictate That Every Team Uses The Same Tools Cost savings and overall efficiency vs autonomy and buy-in Your team know the best tools but set some principles: " Well supported " Open source (with recent PRs) " Uses existing team skill set @stephenjanaway
  42. 42. Don’t Write From Scratch " It’s expensive " It wastes previous experience " It locks knowledge in a few people's heads " Most production code isn’t written this way @stephenjanaway
  43. 43. Care about a test automation project just like any other project Test automation projects are so often treated we less rigor and care " Scope creep is bad " It should deliver " Don’t change language or framework halfway through " Think about requirements " Same language, same repo, same review processes, CI
 @stephenjanaway
  44. 44. Automation Goes Stale Even if you have a suitable number of automated test cases: " More features = more tests " New test for every bug = more tests " More tests = bloated test suites " Bloated test suites = less efficient testing You need a plan to manage growth @stephenjanaway
  45. 45. Focus On The Outcome - Failing and Passing Checks " You need a process to review results " Triage " Dashboards " Stale tests " Don’t forget why you are testing in the first place @stephenjanaway
  46. 46. Hint... You aren’t there to make the automated tests pass @stephenjanaway
  47. 47. Photo: https://www.flickr.com/photos/cgrusden/ “Good testing involves balancing the need to mitigate risk against the risk of trying to gather too much information” Jerry Weinberg @stephenjanaway
  48. 48. Train them Find the people What Is Automation anyway? Start here Build a great team Get it live What should you care about? Saving the world Choose a tool So We Went On a Journey Plan your project End here Now what?
  49. 49. What Have I Learnt? " You need the right amount of test automation " Separate automation teams are a bad thing " Small cross functional teams owning test automation are a good thing " People will promise that test automation solves every problem you have. It doesn’t " Treat test automation just like production code " Treat test automation projects just like production projects " Hire with care " Invest in training but don’t expect your people to do it (all) " Don’t forget why you are testing in the first place " You need exploratory testers too @stephenjanaway
  50. 50. Everyone Is Responsible For Quality @stephenjanaway
  51. 51. Stephen Janaway @stephenjanaway stephenjanaway.co.uk testinginthepub.com

×