Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (9)
Semelhante a Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plenary session at Agile Roots 2015
Semelhante a Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plenary session at Agile Roots 2015 (20)
Mais de lisacrispin
Mais de lisacrispin (15)
Último
Último (20)
Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plenary session at Agile Roots 2015
- 1. Do Testers Have to Code… Agile Roots Utah June, 2015 Lisa Crispin Janet Gregory @lisacrispin @janetgregoryca to be useful?
- 2. A little about us Janet First agile team: 2000 Currently coaching, training Twitter: janetgregoryca Email: janet@agiletester.ca Agile Testing; 2009 More Agile Testing: Oct 2014 Website: www.agiletester.com www.agiletester.ca Lisa First agile team – 2000 Currently tester on Pivotal Tracker team Twitter: lisacrispin Email: lisa@agiletester.ca
- 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. We need to automate everything! Let’s hire some SDETs! But shouldn’t we be trying to build quality in?
- 5. Reality Check… • Many (if not most) job ads ask for programming skills • Managers think test automation is a silver bullet • Technical skills help testers communicate with devs, ops, others
- 6. Our take • Testing skills such as exploratory testing are a must • Competencies trump roles • The whole team must take responsibility for quality • Testing starts at the beginning • Know what you need to add value • There is no room for zombie testers!
- 8. Breadth of Skills DepthofSkills Square-shaped Team See links for more by Rob Lambert and Adam P. Knight
- 9. Testers need Technical Awareness !! Agile teams already have coders, but…
- 10. This means learning… • Testing 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
- 12. IDEs (integrated development environment) If you use same tools as teammates… …they can more easily help you
- 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. Frameworks / languages / terminology Example of BDD format Given the user has no existing account When she requests to create a new account And she enters a valid user name and valid password (rules defined) Then the information is saved upon submitting.
- 15. Testing Skills
- 17. Thinking Skills
- 18. Examples of thinking skills • Collaborating, communicating • Eliciting examples • Asking questions • Getting/delivering info: “Show me”
- 19. Sticker by Brian Marick
- 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.
- 22. Testers add unique value • Delivery teams already have coders • But may not have testing skills such as: • Exploratory testing • Specialties such as security, performance, UX testing • Eliciting examples from customers, turning into tests that guide coding
- 23. So, do we need to be coders? • Dev teams already have coders! • Technical awareness is a must • Thinking skills enable our contributions • Specialized testing skills add huge value
- 24. Where to get the skills? Experiment! • Study group, book club • Community of Practice • Online resources • What fits your learning style? • Find the wonder!
- 25. There’s not one right way Find ways testers can add value to your team And then …. keep learning
- 26. More Learning • Adzic, Gojko, Specification by Example: How Successful Teams Deliver the Right Software, Manning, 2011 • Adzic, Gojko, Impact Mapping: Making a Big Impact with Software Products and Projects, 2012a http://impactmapping.org • Gärtner, Markus, ATDD By Example: A Practical Guide to Acceptance Test-Driven Development, Addison-Wesley, 2012a • Karten, Naomi, "Are You Listening?", http://www.agileconnection.com/article/are-you-listening, Agile Connection, 2009 • Keogh, Liz, http://lunivore.com - look for her posts on BDD, Real Options • Knight, Adam P., "T-shaped Tester, Square Shaped Team", http://thesocialtester.co.uk/t-shaped-tester-square-shaped-team/, 2013 • Lambert, Rob, "T-shaped Testers and Their Role In a Team", http://thesocialtester.co.uk/t-shaped-testers-and-their-role-in-a-team/ , 2012 • Levison, Mark, "The Beginner's Mind - An Approach to Listening", http://www.infoq.com/news/2008/08/beginners_mind, InfoQ, 2008 • McMillan, Darren, "Mind Mapping 101", for Testing: http://www.bettertesting.co.uk/content/?p=956, 2011 • Patton, Jeff, User Story Mapping, 2014 • Wynne, Matt and Aslak Hellesoy, The Cucumber Book: Behavior-Driven Development for Testers and Developers, Pragmatic Programmers, 2012
- 27. Agile Testing: A Practical Guide for Testers and Agile Teams More Agile Testing: Learning Journeys for the Whole Team By Janet Gregory and Lisa Crispin www.agiletester.ca www.agiletester.com Contact info www.janetgregory.ca Email: janet@agiletester.ca Twitter: janetgregoryca 27 lisacrispin.com Email: lisa@agiletester.ca Twitter: lisacrispin
Notas do Editor
- 11:20 – the schedule shows us starting at 11:15, but, better to allow for starting late
- Each of us introduces ourselves briefly
- Janet – JR story Poll audience – how many have heard it? How may believe it?
- Lisa Lots of job postings for SDETs – ppl are still saying we need to automate all the things - by itself, doesn’t build in quality.
- Lisa Source – Elisabeth’s blog http://testobsessed.com/?s=testers+code&submit.x=0&submit.y=0 – tho it is 5 years old now, I think there is even more emphasis on programming, automation Lisa – story about learning from teammates why they wanted someone with coding experience
- Janet We live in unicorn land! And it is what we must do even if not everyone does it now. End 11:26
- Lisa 11:26 T-shaped skills are a metaphor to describe the abilities of an agile team member. Focus on skills, competencies rather than roles The horizontal bar represents a broad skill set: the ability to collaborate across disciplines with experts in other areas and to apply knowledge in areas of expertise other than one's own. Generalizing specialist. The vertical bar on the T represents the depth of related skills and expertise in a single field Testers can indeed be proactive and learn many skills to add value to their team. They will talk about how can testers can expand their roles rather than reduce them <Thinking skills, honing your craft> <Dev-Tester Pairing> <Product owners can accept a user story, seeing it does what she expected. However, she may not consider other areas important to customer – performance, risky edge cases, security – tell story of how our team has both PO and testers look at each story> I think we can dilute our skills if we try to be everything. I was talking to someone the other day, who dropped out of programming because they couldn’t keep up with all the technical things they needed to know. Story from agile testing group - once a dev has committed passing code, he coordinates with the tester to establish a window to push to the QA server, as well as the functionality of the code in the push. We're working toward involving the tester more in the design and test authoring phase so that she has a better understanding when she starts testing exactly what's going on.
- Lisa – example, domain knowledge & db expertise – I can help DBA and vice versa End 11:30
- 11:30 Lisa 3 examples: programming concepts, test environments, guiding dev, We can build up our own toolboxes, learn enough to collaborate to solve problems.
- Lisa End 11:54
- Lisa Common vocabulary, be able to understand high level architecture Lisa’s TCL example Brian’s book – OO concepts, automating, pgming terminology Design patterns – common language
- Lisa Get a sys admin or pgmr on your team to help you install IDE they use, set up your team’s project(s). Edit test automation code as well as production code. Integrated w/ source code control. It’s a test management tool! You don’t have to be able to build or run unit tests, though that is a bonus. Also – get a high level overview of system architecture. Programmers will be happy to explain it.
- Janet The story + high level acceptance test, and the conversation exploring examples.
- Janet This is the start of the executable test. Collaborate with programmers to automate it, make it something customers can understand, hide the details, but it helps us know when we’re done. We can still write the tests – we don’t have to automate the code behind it. End 11:38
- Start 11:38
- Janet This is an example of the specialized skills testers bring to the party. Other people on the team can code. But they probably can’t do this. Tours Personas Workflows Risks Other skills might include test design, performance, security End 11:41
- Janet 11:41 Some call these “soft skills”, but that makes them sound easy or not worth much. They take time and effort to practice and learn.
- Janet Ties back to the common language – but we need more than knowing the jargon, technical terms
- Janet Concrete examples are great ways to communicate – use pictures, sketches – anything to help get the point across Ends 11:46
- 11:46 Janet
- Story about Europe 1rst floor, vs 2nd floor in north america cultures. Debrief starts 11:50 ends 11:53
- Lisa 11:53 – ends 11:54
- Starts 11:54 Lisa
- Ends 11:59 Janet / Lisa IF time – share stories, next slide
- 27