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.

Do testers have to code... to be useful?

446 views

Published on

ExpoQA 2016 Lisa Crispin and Raji Bhamidipati

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Do testers have to code... to be useful?

  1. 1. Do Testers Have To Code… to be useful? Lisa Crispin and Raji Bhamidipati @lisacrispin @raji_bh With material from Janet Gregory
  2. 2. A little about us Lisa (with Janet Gregory): Agile Tes)ng 2009 More Agile Tes)ng: 2014 @lisacrispin www.lisacrispin.com www.agiletester.ca Raji BhamidipaE So you want to be a scrum master? 2016 @raji_bh www.raji.me 2
  3. 3. We’ve heard it since the dawn of “agile”… Everyone on the team should be able to do everything, including writing production code
  4. 4. We need to automate everything! Let’s hire some SDETs! But shouldn’t we be trying to build quality in?
  5. 5. Reality Check… •  Many (if not most) job ads ask for programming skills •  Managers think test automaEon is a silver bullet •  Technical skills help testers communicate with devs, ops, others
  6. 6. Our take •  TesEng skills such as exploratory tesEng are a must •  Competencies trump roles •  The whole team must take responsibility for quality •  TesEng starts at the beginning •  Know what you need to add value •  There is no room for zombie testers!
  7. 7. MulE- discipline skills Expert Discipline skills T-Shaped Skills
  8. 8. Breadth of Skills DepthofSkills Square-shaped Team See links for more by Rob Lambert and Adam P. Knight
  9. 9. Testers need Technical Awareness !! Agile teams already have coders, but…
  10. 10. This means learning… •  TesEng framework your team selects •  and the DSL (domain specific language) •  Common language with programmers •  Common language with customers •  Code to read & understand •  Code to write? – can’t hurt, but not absolutely required •  Domain knowledge
  11. 11. Understand Programming Concepts Common vocabulary
  12. 12. IDEs (integrated development environment) If you use same tools as teammates… …they can more easily help you
  13. 13. Feature (with examples) User Story High- Level AT Fix Defects Code, test & automate story ATDD Acceptance Test Driven Development Accept Story Explore Examples
  14. 14. Frameworks / languages / terminology Example of BDD format Given the user has no exisEng account When she requests to create a new account And she enters a valid user name and valid password (rules defined) Then the informaEon is saved upon submifng.
  15. 15. Testing Skills
  16. 16. Workflows, Journeys
  17. 17. Thinking Skills
  18. 18. Examples of thinking skills •  CollaboraEng, communicaEng •  EliciEng examples •  Asking quesEons •  Gefng/delivering info: “Show me”
  19. 19. SEcker by Brian Marick
  20. 20. 1.  Find a pair 2.  One person faces away from the screen 3.  The other person will have 2 -3 minutes to describe the picture I show next 4.  When I say stop, turn around and discuss any differences in what was described.
  21. 21. Testers add unique value •  Delivery teams already have coders •  But may not have tesEng skills such as: •  Exploratory tesEng •  SpecialEes such as security, performance, UX tesEng •  EliciEng examples from customers, turning into tests that guide coding
  22. 22. So, do we need to be coders? •  Dev teams already have coders! •  Technical awareness is a must •  Thinking skills enable our contribuEons •  Specialized tesEng skills add huge value
  23. 23. Where to get the skills? Experiment! •  Study group, book club •  Community of PracEce •  Online resources •  What fits your learning style? •  Find the wonder!
  24. 24. There’s not one right way Find ways testers can add value to your team And then …. keep learning
  25. 25. More Learning •  Adzic, Gojko, Specifica)on by Example: How Successful Teams Deliver the Right SoDware, Manning, 2011 •  Adzic, Gojko, Impact Mapping: Making a Big Impact with SoDware Products and Projects, 2012a hnp://impactmapping.org •  Gärtner, Markus, ATDD By Example: A Prac)cal Guide to Acceptance Test- Driven Development, Addison-Wesley, 2012a •  Karten, Naomi, "Are You Listening?", hnp://www.agileconnecEon.com/arEcle/ are-you-listening, Agile ConnecEon, 2009 •  Keogh, Liz, hnp://lunivore.com - look for her posts on BDD, Real OpEons •  Knight, Adam P., "T-shaped Tester, Square Shaped Team", hnp:// thesocialtester.co.uk/t-shaped-tester-square-shaped-team/, 2013 •  Lambert, Rob, "T-shaped Testers and Their Role In a Team", hnp:// thesocialtester.co.uk/t-shaped-testers-and-their-role-in-a-team/ , 2012 •  Levison, Mark, "The Beginner's Mind - An Approach to Listening", hnp:// www.infoq.com/news/2008/08/beginners_mind, InfoQ, 2008 •  McMillan, Darren, "Mind Mapping 101", for TesEng: hnp:// www.benertesEng.co.uk/content/?p=956, 2011 •  Panon, Jeff, User Story Mapping, 2014 •  Wynne, Man and Aslak Hellesoy, The Cucumber Book: Behavior-Driven Development for Testers and Developers, PragmaEc Programmers, 2012
  26. 26. Agile Tes)ng: A Prac)cal Guide for Testers and Agile Teams More Agile Tes)ng: Learning Journeys for the Whole Team www.agiletester.ca, www.lisacrispin.com Email: lisa@lisacrispin.com 27 Save 35%: hnp://informit.com/ swtesEng or hnp://informit.com/ agiletest Use code AGILETESTING
  27. 27. Enjoy your learning journey! 28

×