Knights of Quality: Immersive talk about software testing
0 likes16 views
Kari Kakkonen discusses his journey and contributions to software testing, focusing on teaching testing concepts to children through the book 'Dragons Out!', which uses fantasy to engage young learners. The presentation highlights various defects found in software and introduces approaches for effective learning in both children and adults. Kakkonen emphasizes the importance of integrating testing education into coding curricula to address the growing demand for software testers.
Knights of Quality: Immersive talk about software testing
- 2. Knights of Quality – an Immersive talk about software testing Kari Kakkonen, Dragons Out Oy & Knowit Solutions Oy At Findmore Academy Online Nov 11, 2023 © Dragons Out Oy 2
- 3. Kari’s journey into a Knight of Quality © Dragons Out Oy 3 • Eager testing salesperson • Trainer • Consultant • Consulting, Assessments, • Test manager, • National level volunteer (FiSTB, FAST) • International level (ISTQB) • Speaking, training • Authoring testing books • Leadership in international associations (ISTQB, TMMi) • Educating testing to children • Integration of testing into Agile and DevOps
- 4. 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 • Tester of the Year in Finland 2021 • EuroSTAR Testing Excellence Award 2021 • Exemplary DevOps Instructor Award 2023 by DASA • 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 Kari Kakkonen, Lead Testing Consultant SERVICES • ISTQB Advanced, Foundation, Agile Testing, AI Testing • Knowit Quality Professional • DASA DevOps • Quality & Test process and organization development, Metrics, TMMi and other assessments • Agile testing, Scrum, Kanban, Lean • Leadership • Test automation, Mobile, Cloud, DevOps, AI • Quality, cost, benefits EDUCATION • ISTQB Expert Level Test Management & Advanced Full & Agile Tester certified • DASA DevOps, Scrum Master and SAFe certified • TMMi Professional, Assessor, Process Improver 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, telecommunications, commerce, Insurance, banking, pension. 11.10.2023 4 twitter.com/kkakkonen dragonsout.com act2lead.net MORE INFORMATION linkedin.com/in/karikakkonen/ © Copyright Knowit Trainings 2023
- 5. A Nordic powerhouse for digital solutions 4 400+ Experts 6 countries SE, NO, FI, DK, DE, PL 613 MEUR Combined turnover 2022 4 business areas Solutions, Experience, Connectivity and Insight Nordic ESG-ambassador Clear vision to accelerate the UN sustainability agenda
- 6. The book project ”Dragons Out!” • Mission • “Software testing brought to children” • Book • Author Kari Kakkonen • Illustrator Adrienn Széll • Text and illustration rights Dragons Out Oy • In Finnish, English, Polish, French and growing • For ages of 10-99 • Free “Dragon lesson in software testing” presentation under Creative Commons –license • Translated to 20 languages! • More info: www.dragonsout.com • Also other books coming out 6
- 7. ISTQB GLOBAL PRESENCE • Number of exams administered: over 1,2 million • Number of certifications issued: 845,000 • In 130 countries
- 8. TMMi for test improvement in all kinds of testing, including agile and DevOps
- 9. Agenda • Book project recap • Why teach software testing to children • Fantasy as a way to teach software testing • What can we learn from how children learn into how adults learn • Q&A © Dragons Out Oy 9
- 10. The book project recap 10 © Dragons Out Oy
- 11. 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 11 https://medium.com/@docjamesw/the-storytelling-manifesto-f17548a358b3
- 12. 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 12
- 13. 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 13
- 14. 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 14
- 15. Fantasy as a way to learn software testing 15 © Dragons Out Oy
- 16. 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 16
- 17. What is software? • There is software everywhere, in games, online stores or car steering systems, in the same way as a fantasy world is full of castles and villages. • A software can also run a device. • Also called a program, although actually many programs make up a software. 11.10.2023 © Dragons Out Oy 17 Software = computer code that allows a person to do something, such as play a game. Also, the software product.
- 18. What is a defect? • Every software has defects, as it is human to make mistakes. • Defects make the use of software more difficult, in the same way as dragons harass castles and their inhabitants in fantasy stories. • Defects are in the software by accident, and they must be removed, preferably before a software user finds them. • A defect is often called a bug. 11.10.2023 © Dragons Out Oy 18 Defect = a problem in the software code that causes a failure in software. People sometimes call it an error, even though, strictly speaking, an error is a human act that results in a defect in the code.
- 19. 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 19
- 20. 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 20
- 21. Robbing dragons © Dragons Out Oy 21 • 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
- 22. 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 22
- 23. 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 23
- 24. 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 24
- 25. 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 25
- 26. 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 26
- 27. 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 27
- 28. 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 28
- 29. Knights © Dragons Out Oy 29 • Developers • Programmers, coders • Testers • Work together, usually in the same development team (Agile) • Build software • Test software • Find and fix defects
- 30. Children, villagers © Dragons Out Oy 30 • Users • Help build software • Test new software • Test old software • Ask for help from technical support and developers, when needed
- 31. Hunters © Dragons Out Oy 31 • 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)
- 32. Lords and Ladies © Dragons Out Oy 32 • Order software and systems • Product owners • Management • Define what the software should do • Listen to developers
- 33. Sages © Dragons Out Oy 33 • Experts in • Usability • Security • Performance • Help product owners • Help development teams
- 34. Interesting ways of learning for children 34 © Dragons Out Oy
- 35. 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
- 36. 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.
- 37. 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
- 38. 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
- 39. 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/
- 40. 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/
- 41. 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/
- 42. 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
- 43. 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 43