How Children Learn Testing Kari Kakkonen Odin conference.pdf
0 likes18 views
The document highlights Kari Kakkonen's efforts to promote software testing education for children through the book 'Dragons Out!', emphasizing the importance of making testing familiar at a young age. It discusses various educational methods such as storytelling and hands-on learning which appeal to different learning styles and age groups, particularly tweens. The text advocates for integrating software testing skills early on, given the increasing interest in coding among youth and the significant role of testing in software development.
How Children Learn Testing Kari Kakkonen Odin conference.pdf
- 1. © Dragons Out Oy 1
- 2. How children learn testing with dragons Kari Kakkonen, Dragons Out Oy & Knowit Oy At ODIN 2021, Oslo, Norway November 25th, 2021 © Dragons Out Oy 2
- 3. • ROLES • Knowit Solutions Oy, Director of Training and Competences, Lead Consultant, Trainer and Coach • Children’s and testing author at Dragons Out Oy • TMMi, Board of Directors • Treasurer of Finnish Software Testing Board (FiSTB) • ACHIEVEMENTS • ISTQB Executive Committee 2015-2021 • Influencing testing since 1996 • Ranked in 100 most influential IT persons in Finland (Tivi magazine) • Great number of presentations in Finnish and international conferences • TestausOSY/FAST founding member. • Co-author of Agile Testing Foundations book • Regular blogger in Tivi-magazine • EDUCATION • ISTQB Expert Level Test Management & Advanced Full & Agile Tester certified • DASA DevOps, Scrum Master and SAFe certified • SPICE provisionary assessor certified • M.Sc.(Eng), Helsinki University of Technology (present Aalto University), Otaniemi, Espoo • Marketing studies, University of Wisconsin-Madison, the USA. BUSINESS DOMAINS • Wide spread of business domain knowledge • Embedded, Industry, Public, • Training, Telecom, Commerce, • Insurance, Banking, Pension SERVICES • ISTQB Advanced, Foundation and Agile Testing • A4Q AI and Software Testing • Knowit Quality Professional • DASA DevOps • Quality & Test process and organization development, Metrics • Agile testing, Scrum, Kanban, Lean • Leadership • Test automation, Mobile, Cloud, DevOps, AI • Quality, Cost, Benefits. Kari Kakkonen twitter.com/kkakkonen linkedin.com/in/karikakkonen/ Dragonsout.com © Dragons Out Oy 3
- 4. Creating a Nordic powerhouse for digital solutions with a sustainable impact 4 2 3,800+ / Experts 6 Countries / Sweden, Norway, Finland, Denmark, Germany and Poland 545 M € / Liikevaihto 54,3 M € / EBITA 4 Business Areas / Solutions, Experience, Insight ja Connectivity Nordic ESG champions / Clear vision to accelerate the UN Environment, Social, Governance, and Sustainable Development agenda
- 5. ISTQB GLOBAL PRESENCE • Number of exams administered: 1 030,000 • Number of certifications issued: 750,000 • In 129 countries
- 6. Agenda • Book project recap • Fantasy as a way to learn software testing • Feedback survey results from book readers • Interesting ways of learning for children • Interesting ways of learning for adults • Exercise: Draw your own dragon • Q&A © Dragons Out Oy 6
- 7. The book project recap 7 © Dragons Out Oy
- 8. I want to tell a story “Every person has a story. Every cause needs a storyteller. Learn to be a storyteller because unless you are a candidate for a reality show, no one else is going to tell your story for you. So tell us a story. Tell us a good story. And let that good story be one part of a symphony of stories that makes this world a better place.” James Whittaker © Dragons Out Oy 8 https://medium.com/@docjamesw/the-storytelling-manifesto-f17548a358b3
- 9. Why testing for children? • Coding has started to interest children and youth. • Many parties in our societies promote coding e.g. via coding schools • There is not enough software testing education • Testing is even over half of all software development work • There is also a lack of testers, not only a lack of coders • Testing is the new basic skill • Good quality is needed in software development in Finland and around the world • We need to make software testing familiar already to children • Testing schools • Testing books • My own solution, on top of all the coding schools, is to offer children a book about software testing © Dragons Out Oy 9
- 10. Book project highlights © Dragons Out Oy 2014 2018 2019 2020 2021 Linda Liukas publishes Hello Ruby We need also a testing book for children! To the sabbatical writing time! Crowdfunding campaign School donation campaign Now there’s time! Illustration! Recipients: Schools Donations: IT- companies! Great feedback! Fantastic visuals! Great feedback! Published 1.12.2020 Authoring: Finnish Dragons Out! -book Illustration and Sample design Authoring: English Dragons Out! book . . . Publishing: English Dragons Out! -book Published 30.7.2021 Publishing: Finnish Dragons Out! -book 10
- 11. About the book ”Dragons Out!” • Author Kari Kakkonen • Illustrator Adrienn Széll • Text and illustration rights Dragons Out Oy • A version of this presentation is available for teachers (or anyone) under Creative Commons –license at the book web site • Translated to many languages! • More info: www.dragonsout.com © Dragons Out Oy 11
- 12. Fantasy as a way to learn software testing 12 © Dragons Out Oy
- 13. Power of the story Story • Swanlake turned her horse around and rode fast back to the palisade. She called to the knights and building master Aidan that the dragon was coming. All the sharpened trunks needed to be moved urgently to the hole in the palisade. Spears and swords, whoever had them, should be fetched immediately. All available water should be poured into buckets. Then she went to find Yellowbeard at the castle. Explanation • In the story the dragon arrives to a village in the middle of the repairs of the palisade. Similarly, most of the defects are found in software during software development, before the software is released. Then the people who look for defects (testers) and fix defects (coders), are always available. Usually a tester finds the defect, so doesn’t wait for a user to find the defect later. In this story Swanlake was a tester who found and identified the defect, that is the dragon. As a tester she couldn’t this time fix the defect but needed coders (developers) to help. © Dragons Out Oy 13
- 14. Annoying dragon • Color: Red • Size: Medium • How difficult to find?: Difficult • How difficult to get rid of?: Easy • Flies?: No • Wings: Small • Breaths fire?: Yes • Favorite thing: Eating lambs © Dragons Out Oy 14
- 15. Annoying dragon • Defect name: Memory leak • Severity: Medium • Defect symptoms: The computer gets slower, until it can’t function at all, and it shuts down • Cause of the defect: Memory is reserved for use of the software, but it is not freed after usage • Root causes: Developer is not careful in freeing the memory. May not know how, may not remember. • Testing: You measure used memory as you use the software. If the amount of used memory increases all the time, it is probably a memory leak. • Fix: You run the software one line of code at a time, until you find the spot that should be fixed. Memory is released with a proper piece of code. © Dragons Out Oy 15
- 16. Robbing dragons © Dragons Out Oy 16 • Color: Glittering green, or gray • Size: Small to large • How difficult to find?: Easy to difficult • How difficult to get rid of?: Easy to difficult • Flies?: Some fly, some don’t • Wings: Small to large • Breaths fire?: Yes • Favorite thing: Stealing food and treasure
- 17. Robbing dragons • Defect name: Functionality defects • Severity: Low-Medium-High • Defect symptoms: The software doesn’t do what it should do. Calculation gives wrong result. User sees information in the wrong place. • Cause of the defect: The functionality has been coded wrong. • Root causes: Developer has not understood, what the user has meant. Or the defect exists due to carelessness, or hurry. • Testing: You use the software normally, based on tester experience or requirement definitions. • Fix: Code is changed to work correctly. © Dragons Out Oy 17
- 18. Mean dragon • Color: Black • Size: Small • How difficult to find?: Difficult • How difficult to get rid of?: Medium • Flies?: Yes • Wings: Medium • Breaths fire?: A lot • Favorite thing: Stealing food and treasure without being detected © Dragons Out Oy 18
- 19. Mean dragon • Defect name: Security defect • Severity: High • Defect symptoms: Information from the software is found outside the system (e.g. bank card information). It could also be just software functioning wrong. • Cause of the defect: A criminal has used security defect to break into the system, and then has stolen or destroyed something. • Root causes: Developer has not followed the latest secure coding principles. Maybe doesn’t know these. • Testing: You look for known vulnerabilities in the software by using it, or via a security testing software. You can also review code. Checklist of known defects helps. • Fix: A known vulnerability has also a known fix. It is fixed in the code or system settings. © Dragons Out Oy 19
- 20. Underground dragon • Color: Brown • Size: Large • How difficult to find?: Easy • How difficult to get rid of?: Medium • Flies?: No • Wings: Small • Breaths fire?: A lot • Favorite thing: Finding easy food and eating © Dragons Out Oy 20
- 21. Underground dragon • Defect name: Hardware defect • Severity: High • Defect symptoms: Some part of or all of the computer doesn’t work. • Cause of the defect: A part of hardware has broken over time. • Root causes: A part of hardware may be of low quality, so it doesn’t last as long as it should. Possibly the part doesn’t work well with other parts, so it breaks. • Testing: You use the system normally. You observe the hardware. Test environment uses similar hardware than the users will have. • Fix: You change a broken part to a new one or change to a part that better fits other parts. © Dragons Out Oy 21
- 22. Nice dragon • Color: Glittering green • Size: Medium • How difficult to find?: Easy • How difficult to get rid of?: Easy • Flies?: Yes • Wings: Medium • Breaths fire?: Yes • Favorite thing: Eating animals and helping people © Dragons Out Oy 22
- 23. Nice dragon • Defect name: Defect seeding, mutation testing - a defect created on purpose • Severity: Low • Defect symptoms: It looks like the functionality works wrong, e.g. wrong result from a calculation. So, the defect looks like a functionality defect. • Cause of the defect: Tester or coder has created the defect into the code on purpose. • Root causes: The idea is that when all seeded defects have been found, all defects have been found. • Testing: You use the system normally and try to find all seeded defects. You will also find real defects. When the last seeded defect is found, you can stop testing. • Fix: Remember to fix the code also for the seeded defects, in the same way as for real functionality defects. © Dragons Out Oy 23
- 24. Knights © Dragons Out Oy 24 • Developers • Programmers, coders • Testers • Work together, usually in the same development team (Agile) • Build software • Test software • Find and fix defects
- 25. Children, villagers © Dragons Out Oy 25 • Users • Help build software • Test new software • Test old software • Ask for help from technical support and developers, when needed
- 26. Hunters © Dragons Out Oy 26 • Technical support • Maintain the software / system • Test • Fix defects • Help users • Ask for help from developers when needed • Sometimes in the development team (DevOps team)
- 27. Lords and Ladies © Dragons Out Oy 27 • Order software and systems • Product owners • Management • Define what the software should do • Listen to developers
- 28. Sages © Dragons Out Oy 28 • Experts in • Usability • Security • Performance • Help product owners • Help development teams
- 29. Feedback survey results from book readers 29 © Dragons Out Oy
- 30. About collecting feedback • I've run a survey to teachers in Finland about what kind of learning approach has worked best for students of different ages. • The biggest interest has been in age groups 10-15. • The feedback is great. • Survey results combined with verbal feedback from teachers • On a scale from 1-5 the book/testing rates 4,22 • Numbers are small and thus should be treated as tentative • However, the responses reveal interesting views
- 31. Software Testing coupled with fantasy fits to many teaching subjects • Multiple teaching subjects are covered • Phenomena learning • Coding is most (not surprisingly) best match with software testing N=8
- 32. What interests children about the topic? • Fantasy works best in creating attraction • Learning of software testing comes as a side effect • A book is preferred over powerpoint lesson (ppt) N=8
- 33. What are best situations to teach with a software testing book? • Teacher assisted learning (classes) gets highest rating even though books can of course be read individually • Organized learning is best! N=8
- 34. Combining learning approaches • It has been fascinating to see how combining different learning approaches works in getting enthusiastic learners into software testing. • The usual combination has been • drawing exercises • listening or reading testing content • understanding through the power of analogies between fantasy and software testing • exploratory testing.
- 35. Interesting ways of learning for children 35 © Dragons Out Oy
- 36. How children learn? • Stories, examples • Identifying with others, Idols • Imitating • Rhymes, songs • Playing, games • Exploring, doing, trial and error • Simplicity, clarity • Repeating • Remembering • Boundaries (right and wrong) © Dragons Out Oy 36
- 37. Many learning strategies is a good thing • “Children and teenagers learn by observing, listening, exploring, experimenting and asking questions” (1) • “The broader the range of strategies that children can use appropriately, the more successful they can be in problem solving, in reading, in text comprehension and in memorizing. “ (2) © Dragons Out Oy 37 1 https://raisingchildren.net.au/school-age/school-learning/learning-ideas/learning-school-years 2 http://www.ibe.unesco.org/sites/default/files/resources/edu-practices_07_eng.pdf
- 38. Storytelling works for all learning styles • Visual learners like the mental pictures they get from storytelling • Auditory learners connect with the words and the storyteller’s voice. • Kinesthetic learners can hook into the emotional connections and feelings from the story. • Storytelling also helps with learning because stories are easy to remember © Dragons Out Oy https://www.harvardbusiness.org/what-makes-storytelling-so-effective-for-learning
- 39. Focus on 10-12 year olds or “Tweens” • “Around the age of 11 or 12, children learn to think about abstract concepts.” • “Tweens display strong metacognition skills, i.e. ability to think about thinking. Children display this ability through an awareness of knowledge, an awareness of thinking, and an awareness of thinking strategies.” • Software testing is essentially about thinking what we already know and expanding that knowledge by exploring. © Dragons Out Oy 39 https://www.scholastic.com/parents/family-life/creativity-and-critical- thinking/development-milestones/cognitive-development-11-13-year-olds.html
- 40. 6 ways for children to learn testing - takeaways • Start with a Fantasy example, explain into ICT-world • Be extremely clear and concise • 5-minutes of theory, 20-minutes of exercise structure • Use all the senses (listen, see, talk, draw dragons) • Use common sharing of exercise results (e.g. Padlet) • Try out your test ideas immediately to an app of your choice
- 41. Interesting ways of learning for adults 41 © Dragons Out Oy
- 42. 6 ways for adults to learn testing - takeaways • Use examples and analogues from real-life • Be extremely clear and concise • Hands-on, mostly exercises in the learning • Use all the senses (listen, see, talk, draw mindmaps) • Use common workspace for real-time status of testing (e.g. Mural, Miro) • Get your hands dirty and test some (buggy) software immediately & explain how you test it • These are extrapolated from the findings how children learn best.
- 43. Analogues, parallells • Talk about day-to-day life to drive your point • Cars • Hobbies • Sports • Pets • Family Pic: https://medium.com/serious-scrum/scrum-s-connection-to-rugby-597405fed5ec
- 44. Clear, concise communication • Express what you mean clearly • Start from big picture • Use concepts that sum it all up, e.g. • Keywords • Mission statements • Vision statements • Values Quote: Farhshad Asl Pic: https://quotefancy.com/quote/1956575/Farshad-Asl-Sharing- a-clear-and-concise-vision-spawns-a-sense-of-purpose-and-direction-It
- 45. Hands-on, exercises • Competencies can be achieved by performing hands-on exercises • Exercises e.g. on • Setting up and using test environments. • Testing applications on virtual and physical devices. • Using tools on desktops and/or mobile devices to test or assist in testing related tasks such as installation, querying, logging, monitoring, taking screenshots etc. • Basically, hands-on learning is learning by doing Source: https://www.istqb.org/downloads/send/61-mobile- application-testing/251-mobile-application-testing-specialist-syllabus.html Pic and source: http://parklandplayers.com/hands-on-learning- what-does-it-mean-and-why-is-it-important/
- 46. Use all the senses • Listen to the teacher • With focus! • See the slides • Before, during, after session • Talk and reflect • What is in it for me? • What is in it for us? • Use your hands • Keep notes • Draw pics • Draw mindmaps Pic and source: https://www.mindmup.com/
- 47. Real-time status of testing • Use Group Memory • Show what is discussed in the class • Record working group tasks • Keep test plans visible • Track test progress in testing exercise • Any sharing tool works • Mural, Miro etc. • Mindmaps • Whiteboard tools Pic: https://www.mural.ly/
- 48. Start testing immediately • Pick a testing approach or technique • Apply immediately • Use software from • The students • Your own company • Startup companies • Record test progress • Record defects • Discuss how you think when you test Pic: https://get.timespace.co/focus/ Source: https://we.knowit.fi/knowit-suomi/win-win-scenario-with-startups
- 49. Design your own dragon (i.e. defect) 49 © Dragons Out Oy
- 50. Competition: Design your own defect – draw your own dragon // What you need Paper and pencil // Task 1 Think of a defect you have encountered - Write down the name of the defect and a few words to describe it 2 Think of an equivalent dragon - Write down characteristics of the dragon. If the defect was bad, the dragon is big etc. 3 Draw the dragon - Main thing is to carry through your idea of how the defect can be represented by the dragon - No need to aim for perfect picture. 4 Email the photo to kari.kakkonen@dragonsout.com - Take a photo of the drawing and send it to me - I’ll make a draw for a lucky winner to receive a copy of the English Dragons Out book 50 © Dragons Out Oy
- 51. Thank you! Order the book: https://www.austinmacauley.com/book/dragons-out Follow and share the book project: • https://www.dragonsout.com • https://www.facebook.com/DragonsOutOy • https://www.instagram.com/dragonsoutbook/ • https://twitter.com/DragonsOutOy • https://www.linkedin.com/company/dragons-out/ Ask questions: kari.kakkonen@dragonsout.com © Dragons Out Oy 51