Kari kakkonen Testing for children at Testing Assembly 2019
1 like417 views
The document discusses the significance of promoting software testing among children by utilizing engaging storytelling techniques, such as dragon analogies, to make the learning process relatable and enjoyable. It highlights the lack of emphasis on testing education despite its critical role in software development and presents a book titled 'Dragons Out!' designed to introduce the concepts of software testing in a fun way. The book is currently seeking crowdfunding to support its publication, aiming to make software testing familiar to future generations.
Kari kakkonen Testing for children at Testing Assembly 2019
- 1. The book about dragons, knights and software testing 22.9.2019 © Dragons Out Oy 1
- 2. Kari Kakkonen • ROLES • Knowit Oy, Director/Quality and Competences, Lead Consultant, Trainer and Coach • Secretary of ISTQB Executive Committee • Treasurer of Finnish Software Testing Board (FiSTB) • Children’s and testing author at Dragons Out Oy • ACHIEVEMENTS • 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 Full & Advanced Full & Agile Tester certified • DASA DevOps Fundamentals, 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 + Knowit Quality Professional • DASA DevOps • Quality & Test process and organization development, Metrics • Agile testing, Scrum, Kanban, Lean • Leadership • Test automation, Mobile, Cloud, DevOps • Quality, Cost, Benefits. Twitter: @kkakkonen LinkedIn: fi.linkedin.com/in/karikakkonen/ 22.9.2019 © Dragons Out Oy 2
- 3. Knowit has offices The company is listed Established 301 000 000 € More than 2 200 Knowit services www.knowit.fi in Sweden, Norway, Finland, Denmark and Germany on the Nordic Exhange in Stockholm in 1990 in net sales 2018 specialist in total. In Helsinki office approx. 130 specialists. Creating Digital Opportunities • Quality Software Development • Intelligent Automation • Software Development Consultancy • Training and Coaching • Client Experience offering 29/22/2019
- 4. ISTQB® 2018 4 ISTQBⓇ GLOBAL PRESENCE Number of exams administered: ~875,000 Number of certifications issued: 641,000+ In Over 120 countries
- 5. Testing for Children - How to get them enthusiastic about testing career at young age? 22.9.2019 © Dragons Out Oy 5
- 6. Agenda • Children need encouragement towards testing, not only coding. • The approach must be fun and story like • Dragon and knight stories offer analogies to testing • Design your own dragon (i.e. defect) 22.9.2019 © Dragons Out Oy 6
- 7. Why testing for youth / children? • Coding has started to interest children and youth. • Many parties in society 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 23.9.2019 © Dragons Out Oy 7
- 8. How do children learn? • Stories, examples • Rhymes, songs • Playing • Games • Exploring, doing, trial and error • Simplicity, clarity • Repeating • Remembering • Identifying with others, Idols • Imitating • Boundaries (right and wrong) 22.9.2019 © Dragons Out Oy 8
- 9. 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. 22.9.2019 © Dragons Out Oy 9
- 10. 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 22.9.2019 © Dragons Out Oy 10
- 11. 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. 22.9.2019 © Dragons Out Oy 11
- 12. Robbing dragons 22.9.2019 © Dragons Out Oy 12 • 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
- 13. 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. 22.9.2019 © Dragons Out Oy 13
- 14. 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 22.9.2019 © Dragons Out Oy 14
- 15. 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. 23.9.2019 © Dragons Out Oy 15
- 16. Fast dragon • Color: Purple • Size: Small • How difficult to find?: Difficult • How difficult to get rid of?: Difficult • Flies?: Yes • Wings: Large • Breaths fire?: A little • Favorite thing: Stealing gold in secrecy 22.9.2019 © Dragons Out Oy 16
- 17. Fast dragon • Defect name: Performance defect • Severity: Medium • Defect symptoms: Software is slower than it should • Cause of the defect: Part of the code works inefficiently or plain wrong. Settings could be wrong, too. Software then tries to do something unnecessary. This takes time. • Root causes: Performance wasn’t considered during coding. Developer may not know all possibilities of the coding environment. May not have access to rest of the software. • Testing: You use software normally, one or many users at a time, often with a performance testing software. You measure speed, that is response time. • Fix: You change those parts of the code that work slowly. You try a fix and test the speed again. 23.9.2019 © Dragons Out Oy 17
- 18. Showy, troublesome dragon • Color: Green • Size: Large • How difficult to find?: Easy • How difficult to get rid of?: Difficult • Flies?: Yes • Wings: Large • Breaths fire?: A lot • Favorite thing: Stalking gold and protecting its territory 23.9.2019 © Dragons Out Oy 18
- 19. Showy, troublesome dragon • Defect name: Usability defect • Severity: Low • Defect symptoms: Software is hard to use, but it can be done. • Cause of the defect: Coding is done with only functionality in mind, possibly in the easiest way. • Root causes: User needs have not been taken into account in design or coding. Usability may not be understood. • Testing: You use the system normally. You gather opinions about what is easy and what is hard to use. • Fix: You change the code to be easier to use, respecting results from usability testing. 23.9.2019 © 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 22.9.2019 © 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. 23.9.2019 © Dragons Out Oy 21
- 22. Shadow or dragon? • Color: Grey • Size: Small • How difficult to find?: Easy • How difficult to get rid of?: Easy • Flies?: No • Wings: Small • Breaths fire?: Yes • Favorite thing: Confusing people 22.9.2019 © Dragons Out Oy 22
- 23. Shadow or dragon? • Defect name: Testability defect • Severity: Low • Defect symptoms: It looks like the functionality works wrong, e.g. wrong result from a calculation. • Cause of the defect: Tester may have wrong test data or test environment. • Root causes: Tester may be too enthusiastic to find defects. Test environment and test data may not have been planned properly. • Testing: You use the system normally, but you observe the environment and data. Always consider if the testing is the cause of the defect. • Fix: You define test environment and data better. You learn from false alarms. 23.9.2019 © Dragons Out Oy 23
- 24. 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 22.9.2019 © Dragons Out Oy 24
- 25. Nice dragon • Defect name: Defect seeding - 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. 23.9.2019 © Dragons Out Oy 25
- 26. Stubborn dragon • Color: Glittering green • Size: Large • How difficult to find?: Easy • How difficult to get rid of?: Difficult • Flies?: Yes • Wings: Small • Breaths fire?: Yes • Favorite thing: Harassing people repeatedly 22.9.2019 © Dragons Out Oy 26
- 27. Stubborn dragon 23.9.2019 © Dragons Out Oy 27 • Defect name: Version management defect • Severity: Medium • Defect symptoms: A defect, that was already fixed, appears again. This could be a functionality defect. • Cause of the defect: Version management has failed. Coder uses an old part of software, where a newer part should be used. This new part includes a defect fix by another developer. • Root causes: Hurry and too big number of people produce defects. Version management may be missing altogether. • Testing: You use the system normally. If a defect is found, you check if such a defect is fixed already. If so, you investigate how the version management works. • Fix: You improve how version management works. Start using a version management software.
- 28. Confused dragon • Color: Glittering green • Size: Small • How difficult to find?: Easy • How difficult to get rid of?: Easy • Flies?: Yes • Wings: Medium • Breaths fire?: Yes • Favorite thing: Harassing large dragons 22.9.2019 © Dragons Out Oy 28
- 29. Confused dragon • Defect name: Documentation defect • Severity: Low • Defect symptoms: Functionality works in a different way than the documentation says. • Cause of the defect: Plans and guidelines are not aligned with the software. • Root causes: There have been decisions or changes during coding that have created a different software than planned. Documentation has been created based on old plans. • Testing: You use the system normally. If a defect is found, you consider if the software or the documentation is wrong. • Fix: You change either the software or the documentation, so that they match. 23.9.2019 © Dragons Out Oy 29
- 30. Knights 22.9.2019 © Dragons Out Oy 30 • Developers • Programmers, coders • Testers • Work together, usually in the same development team (Agile) • Build software • Test software • Find and fix defects
- 31. Children, villagers 22.9.2019 © Dragons Out Oy 31 • Users • Help build software • Test new software • Test old software • Ask for help from technical support and developers, when needed
- 32. Hunters 22.9.2019 © Dragons Out Oy 32 • 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)
- 33. Lords and Ladies 22.9.2019 © Dragons Out Oy 33 • Order software and systems • Product owners • Management • Define what the software should do • Listen to developers
- 34. Sages 22.9.2019 © Dragons Out Oy 34 • Experts in • Usability • Security • Performance • Help product owners • Help development teams
- 35. Design your own dragon • Supplies • Paper and markers • Task • Think of different dragons / defects • Decide which dragon you want to draw • Maybe a defect you have found yourself • Simplify • What are characteristics of the dragon /defect? Small, large? Hard to find? • Draw • Dragon in the middle of the paper • Dragon characteristics on the other side • Defects characteristics on the other side 22.9.2019 © Dragons Out Oy 35
- 36. What next? • Your thoughts may end up in Dragons Out book • Book about dragons, knights and software testing • For children, youth and adults • Fun way to learn software testing • Lets make software testing familiar to next generations! • The book is now in crowdfunding at Indiegogo https://igg.me/at/dragons-out-book • Buy books or other perks! • Share news about the book to everyone! 22.9.2019 © Dragons Out Oy 36
- 37. About the book ”Dragons Out!” • Author Kari Kakkonen • Illustrator Adrienn Széll • Text and illustration rights Dragons Out Oy • This presentation will later be available under Creative Commons – license at the book web site • More info: www.dragonsout.com 22.9.2019 © Dragons Out Oy 37
- 38. The book about dragons, knights and software testing 22.9.2019 © Dragons Out Oy 38