Skip to content
Melo Podcasts Home
CategoriesLanguagesFollowing

Episode 62 · Software Testing Unleashed - QA, DevEx & Quality Engineering

Children's Book About Testing That Inspired a Future Tester - Kari Kakkonen

16 Jul 2026 · 16 min

Play episode WhatsApp Download

Episode notes

With Kari Kakkonen I talk about what happens when you explain software testing through a fantasy story for children, where dragons are defects and knights are testers. We get into how the analogy grew into a full world covering functional, performance, usability, and security defects, each mapped to a chapter with its own kind of dragon. Kari describes how he tested the book iteratively with children, teachers, testing professionals, and non-IT readers across four rounds, and how a twelve-year-old at a book fair said she wanted testing as a profession after flipping through it. We also touch…

Transcript

Read the transcript · about 2,770 words, follows along as you listen

It's like tissue testing these days, you know, you you need to have a new person to try out the same ideas. I realized that actually there's not too much information about testing to children. So many books for different angles of professionals and testing this, testing that, but not really for testing for children So for adults who are testing professionals, this is actually the thing to do. Try to read and notice these small analogies. I I don't I don't explain why the dragon was black.

So so you can you can try to find the analogy and think why is it is it black. Welcome to Software Testing Unleashed. My name is Richie and And I have another episode from the Testcon 5 conference from Mauritius. My guest was Kari Kakkonen. He was one of the first guests of this episode. Maybe you remember his talk about software testing leadership. Today we talked about his book. that explains software testing with dragons and knights. Why dragons are defects and knights are testers, how children reacted to the story and why a 12-year-old girl now wants to become a tester.

That's all you hear in this episode. Enjoy. Hello Kari, great to have you on the show here. Hello Richie. Glad to be here. It's a great place. We are now on Mauritius here at the Testcon conference. So we we meet everywhere except Germany and Finland. Yeah, seems like yeah, yeah. Conferences around around the world. Yeah. But it's okay. Yeah, yeah. Yeah. And we have uh uh we've uh thought about what can we talk about uh because you have so broad knowledge and so long time being in in testing.

Uh and uh you put out a book about dragons. Yeah And I did, yeah. Five languages at the moment. Five languages. Finnish and English. French, German, Polish. Oh, it's like Harry Potter. Yeah, almost almost. Maybe not as big s success. But yeah, I think it's getting there. Yeah, yeah. But what was the story behind it? Because I cannot get the dragons into quality. It's a good point. It it's um it it started when I wanted to write a book of my own. I didn't quite know which one it would be and how it how I would turn around And then I was thinking that okay w w w what is is there which is not really explored yet and I realized that actually there's not too much information about testing to children.

So many books for different uh angles of professionals, you know, testing this, testing that, but not really for testing for children. And then I was thinking about so how could I Convey a message of testing for children. It needs to be a story. It needs to be a an interesting story. It needs to be something that they want to pick up. Then I uh a book that they want to pick up, so then I was thinking, okay, what um can I make it even more interesting?

Can I can I maybe combine combine my my own passions and so what what do I like? So I actually like fantasy stories quite a bit and and in in many fantasy stories you have knights and you have dragons and they uh battling so so I was playing around with this analogy and then I was quickly able to find a few possible angles. It could be like that. Dragons could be good guys or bad guys. But it didn't that didn't really work when I was playing it with uh the idea verbally with with some some children but but then I tried how about if dragons are defects yeah And so who is going to find those dragons or battle those dragons?

That would be knights. So knights would be testers and developers. So around that key analogy, I was then able to build a whole world of fantasy. Where anything that you see is actually an analogy of our ISTQB world. Yeah, different kind of dragons, different kind of defects, different kind of knights and people and villagers, lords and ladies They all have their place in trying to ensure good quality, you know, do software testing, remove defects, build better software.

Yeah, all these things. So it yeah, yeah, it it was I mean it was the last one. Yeah yeah it is indeed a a good good uh intro book for testing for for any any edges. Actually I I like to say it's for ages from nine to ninety-nine. Yeah. Like we say in in games. Of course most of the readers are are probably children and and adults. who uh like to explain how how it you know what testing is to their their kids and also teachers who who um who want to you know, bring software testing and and as an extension the whole IT and coding and testing all of that in in into their schools and into their classes.

So it's also been used there. Ah, that's great. And um not not to spoil it too much, but can you give us some examples? What does this this the story the storyline uh in the book Yeah yeah so uh we uh m m mainly there are two two kids, uh girl and a and a boy who are uh finding these uh interesting things happening, uh finding dragons and then suddenly there's also a knight and then they start getting enthusiastic about yeah yeah we we also want to help the knights and you know they want to help find different dragons and and get rid of them or even even make friends with dragons.

Whatever, but you know, so that we drag dragons wouldn't be harmful. So that yeah and the story grows bit by bit they we meet different Kind kinds of dragons and uh and of course as a reader then when you read a book uh every now and then so roughly every page once every page there's a a uh explanation as a text box. So you it's you you see it's a separate thing as a as a storage. So okay what just happened in previous half a half a page was like this.

So you you you you saw the green dragon and that would be the usability defect and and and use it with particular knight and that was a tester with particular skills like that and that so it's always explained out Ah okay. You know, really really spelled out. This is how it is. Yeah, yeah. And and on which parts of the software testing, software quality did you focus in the in the story? Um well it's it's actually Sort of everything. Everything. So the book book structure is that every every uh chapter is a different kind of a quality attribute or quite odd defect.

So there's a functional chapter, there's performance chapter, there's usability chapter, a security chapter. And and so on. So we actually go through um I I was thinking about uh Kim Kahner's famous uh Buck taxonomy. You know, what are what are the different uh bugs or defects that they are and I and I was I was going through that. I was checking okay that that is covered now next chapter okay I'll take that defect covered so so in in that way I was able to cover all um well mm I I skipped a few but most of the uh defekts in in his klassification of backtexonomy.

Yeah, so it it covers everything in a way. It doesn't talk about test automation or AI too much. Okay, so not everything in that sense It hints into these special things, but so I'm I'm leaving something for sekond second versus. Yeah, you need you can upgrade it or the second part in the in the series of whatever. Return to the Dragons or something. Trilogy of I don't know how many parts. Yeah, great. And and uh did you get uh any feedback from from from uh young people they they read the book?

Yeah I did. I I I looked for it. because I I I wrote it iteratively as I as I mentioned. Even with idea I tried with some children. So I had a I had four different rounds. So first chapter round, then one third of a book, two thirds of a book and a whole book. I was always looking into different different um people so I would hear fresh ideas. It's like tissue testing these days. You know, you you need to have a new person to try out the same ideas.

So but I but I I was able to talk to lots of people and I so I I found also adults so I found teachers, I find uh testing professionals, I I I find non-uh IT people and and also children of different ages and and so yeah they they all all read what I had so far and gave nice feedback and encouraged me that this is a good path Yeah. And I I of course I needed to change a few things. Maybe the biggest change was to actually make it the full storyline.

Because originally with different chapters were slightly uh separate but but um mostly they we had these two two two kids all the time there but um but on a few chapters I I had to to To make the analogy I had it had done slightly different but I needed to redo those so that I could make it a continuous story where you you can have these, you can see these two children here all the time. I I can imagine that young people uh they give very hard feedback.

Very honest one. Yeah, I do, I do. But when you get to this nice nice feedback as well. It sounds boring. It's fine. It's not to everybody. But then somebody else especially remember this This girl which was maybe twelve at the book fair where I was showing my books and and and she she came around and and and looked at look at the book back you know uh background and and then uh lifted through a little bit and and she actually said just based on that and and and her mom was there you know I want to buy this book and And you know it it seems so interesting that uh that I actually I want to do it for for profession.

Yeah. It's like wow that's pretty good first impression. Yeah. Yeah, yeah. Yeah, so maybe maybe that's a that's a good good way to to inform about software testing because software testing is still in the when we we look at the school or university part a very very niche format. It's it's not It is, it is. And and even even in Finland where we have in in the curriculum of that government. dISTQBates you have to cover these things. Then we teachers have the uh freedom of how they cover those things.

But they they they're coding coding is mentioned there. So all through elementary school, all the way up to high school you actually need to teach more and more coding. But it's always coding. There's nothing about testing. But of course as an extension many teachers think that okay and they understand you need to test and not only code so so they actually have have taken taken this and and use it as part of their classes of of different natures.

So yeah I've I'm I was quite happy. And actually then when uh when we uh finish an English edition where um published uh together pretty much at the same time same year um I actually uh organized a a campaign of a um a donation campaign where companies and associations, so including many ICQB boards actually, they were able to uh uh purchase uh we pre even pre-order with books and and and then uh after that campaign was was done and we English and Finnish versions were available, they would donate these to local schools.

Oh right. So in Finland I took care of donations myself, so I I distributed we we we donated books to uh about fifty schools and and and then in different countries the different uh ICQB boards did the same for the some some local schools. So that's pretty cool and and it to me it culminated in in in handing a um what I call certificate of donations uh into the uh to the Minister of Education in Finland and so she she accepted that and And also one one copy of a book, of course, and g gave uh great thanks about, you know, helping uh grow our children into better future.

Yeah, yeah, I just worry. That's a good idea. And uh did you have uh do you have any plans to make it um audiobook too or an or um film or something like that? Um no maybe maybe. So I I I um I hired um Adrian Sell to create uh illustration but would be possible simple enough but would would make make it a a 3D character in a in a movie or cartoon or something like that so so Så när jag tänker vad kind of illustrator det ska ha. Okskä illustration, men what kind of illustrator?

Så i was i injuning en styl mit Aidri. that you know uh it it needs to be like this. It it needs to be something that could later, if everything goes nice, it could be a movie or it could be a cartoon. So that's why the drag dragons are Det är simple. Det är väldigt. Det är exakt vad jag envisar. Jag kan dra vet väl. Och aldrig kan. Så vi också vi har vi iterat. Så har du ju. How would you like to see this? And and maybe like third iteration of what she draw was like oh yeah yeah this is what I want.

So yeah let's let's do it like this. Yeah yeah Yeah and we just uh mentioned a few topics which could be in then next uh version or in the next uh t for the trilogy Do you have uh uh also um expect exact uh test automation and AI and other topics you want to put, would you put in into the next issue of that book? I think next one would also be about different techniques and heuristics. Because now it's it's a little bit of explaining uh testing types really.

So you have quality characteristics and then you have related testing types and that's No, that's really what it is. So how how do you exactly find security defects? So there could be a whole chapter about security testing techniques. that that could be in in the next edition. So I think it's techniques, uh automation and AI. Mm-hmm. Oh, that that's interesting how you will map that to that brand story. Yeah, yeah, yeah, exactly, exactly. Actually, and you mentioned adults earlier, so So something I was trying to do all the time was exactly carry the analogy all the way through a book.

So not everything has been spelled out in these text boxes. So for adults who are testing professionals, this is actually the thing to do. Try to read and notice these small analogies. So I I give a hint which I often uh give in a conference talk also also today I think the you know there is a black dragon I I don't I don't explain why dragon is black. So so you can you can try to find the analogy and yeah yeah and and think why is it Okay. Yeah, yeah.

Yeah, so so now we have the open question for the community. They can already sound great. Uh Kari, thank you very much for this insight into the book. We will link it in the show notes, so it's in five languages, so a lot of people can read it. Maybe hear it in the future and see. It is in audio already. In in English we have audio book as well. Ah okay, that's great. We will link that too. Thank you very much. Enjoy the conference here Yeah, I'll see you soon.

Thank you. See you soon. Thank you.

Transcript supplied by the publisher with the episode.

Podcast

Software Testing Unleashed - QA, DevEx & Quality Engineering

Richard Seidl | Software Development & Testing Expert · Business · English

Software testing is no longer just a phase—it’s the foundation of modern engineering and your ultimate competitive advantage. Welcome to Software Testing Unleashed, the weekly podcast for anyone dedicated to building better software, faster. Hosted by Richard Seidl, renowned expert in software deve

More from Software Testing Unleashed - QA, DevEx & Quality Engineering All episodes →

  1. E67 · 20 Aug 2026 · 34 min

    End-to-End Test Automation Without the Maintenance Trap - Lilia Gargouri

    Forty percent of automation time lost to flakiness and maintenance: that is the reality Lilia Gargouri describes. I talked with Lilia about end-to-end test automation at scale, and what struck me most was how far back the real solutions reach: a single HTML attribute added in 2017 still pays dividends today, simply because the team decided to use it consistently and never change it. We get into the full picture, from how to accurately identify every UI element without XPath gymnastics, to why fifteen well-chosen test cases can outperform five hundred noisy ones, to naming conventions and…

  2. E66 · 13 Aug 2026 · 35 min

    API Testing: Agent-Optimized Design Cuts Token Costs - Sebastian Małyska

    With Sebastian Malyska I talk about what sits behind the APIs testers often take for granted. We get into why REST is still on top but not the whole story, how GraphQL and webhooks fit into the picture, and what actually happens when an AI agent talks to a real system through MCP. There is a practical argument running through all of it: if you understand the protocol layer, you can make smarter decisions about where to test, how to structure automation, and how to avoid burning unnecessary tokens and budget. Sebastian also makes the case that front-end testers are already closer to this…

  3. E65 · 6 Aug 2026 · 26 min

    LLMs in Software Testing: Start with Small, Bounded Tasks - Klaudia Dussa-Zieger

    With Klaudia Dussa Zieger I talk about where language models actually deliver in testing and where they fall flat. We get into the concrete details: why a small function like generating keyword documentation works so well with a standard chat model, why reviews only started working once they switched to a reasoning model, and why one engineer working on embedded legacy code said no to AI help without hesitation. Klaudia also shares the translation use case I found most vivid, turning a cryptic technical defect message into something a domain tester can actually read.

  4. E64 · 30 Jul 2026 · 21 min

    Testing Complex Systems: Ship Small and Learn Fast - Jean Francois Riverin

    With Jean-Francois Riverin I get into a question that bothered him for over 20 years: why are there still bugs in production even when you tested as well as you possibly could? His answer is that software stopped being a complicated problem, like building a bridge, a long time ago. It is now complex, more like medicine or meteorology, and that means the whole idea of finding the right answer through testing is the wrong goal. We talk about what it looks like to switch that mindset, what "safe to fail" means in practice, and how to make that argument to a manager who still expects predictable…

  5. E63 · 23 Jul 2026 · 25 min

    Holistic Engineering: Non-Technical Forces Shape Your Code - Vanessa Formicola

    Why do so many software teams end up with the exact architecture they never intended to build? With Vanessa Formicola I talk about the hidden forces that shape technical decisions, and why those forces have far less to do with technology than most engineers want to admit. We get into patterns she calls the kitchen sink, Cirque de Soleil coding, and the monolith constellation, each one a recognizable trap that grows from career incentives, delivery pressure, and organizational culture rather than bad technical judgment. I keep coming back to her concept of holistic engineering, which asks us…

  6. E61 · 9 Jul 2026 · 17 min

    TMMI Level 5: How Mature Teams Stop Bugs Before They Exist - Zsolt Hargitai

    What does it actually take to move from finding defects to preventing them? With Zsolt Hargitai I talk about TMMI, a framework for improving test processes, and why that shift in mindset marks the difference between a team that tests and a team that has genuinely matured. We get into what the maturity levels mean in practice, how a free self-assessment tool on the TMMI website gives you a first impression of where your organization stands, and why the framework holds up across agile, V-model, and DevOps environments alike. I was also curious about the human side: Zsolt mentions that…

  7. E60 · 2 Jul 2026 · 30 min

    Learning and Unlearning with AI: Skills That Outlast Tools - Graziela Tonin

    What does it actually mean to unlearn something, and why does that question matter as much as learning new skills right now? With Graziela Tonin I talk about how universities, companies, and individuals are struggling to find their footing in a world where AI can write code, run tests, and sometimes outperform human decision-making. We get into the research showing that students who offload thinking to AI tools lose cognitive capacity rather than gain it, and what that means for how knowledge should be taught and shared. I keep coming back to her point that the rarest and most durable skills…

  8. E59 · 25 Jun 2026 · 25 min

    Post-Agile: What Organizations Actually Need Now - Michael Mahlberg

    What happens to the teams and organizations left behind after an agile transformation that didn't deliver what it promised? With Michael Mahlberg I talk about why the word "agile" has lost its meaning, how big consultancies pushed companies deeper into rigid structures under an agile label, and what it actually takes to help an organization find its footing again. We get into the question of what genuinely worked from the last 25 years, from fast iterations and real customer feedback to decision-making practices borrowed from outside the agile world entirely. What stays with me is Michael's…

  9. E58 · 18 Jun 2026 · 35 min

    Tester Skills: Communication Decides Whether Bugs Matter - Tara Walton

    What does a tester actually need right now, when AI tools are everywhere and QA teams keep getting cut? With Tara Walton I talk about why communication and the fundamentals of testing matter more than ever, and why being the best bug-finder in the room means nothing if you can't explain what you found and why it counts. We get into how AI's "toxic positivity" makes critical thinking a skill you have to practice deliberately, and what it means that when you remove QA, your users become your first line of defense. I also ask Tara about career direction, and her answer comes back to something…

  10. E57 · 11 Jun 2026 · 21 min

    AI in Regulated Industries: Strategy First in a Medical Lab - Alexis Savkin

    How do you bring AI into a medical lab when the regulatory landscape is still taking shape? With Alexis Savkin I talk about exactly that tension, and the answer turns out to be less about technology than about focus and strategy. We get into why starting with a very specific, measurable problem makes the regulatory side manageable, and how a single-page risk diagram convinced compliance stakeholders faster than any technical pitch. I keep coming back to his point that regulators are not enemies but partners trying to make things safer, and that the real mistake is trying to solve "AI" as one…

Take it with you

The Melo app keeps playing with the screen off, works in the car and on your watch, wakes you to your station, and browses the whole catalogue offline. Free, no ads, no account.

Get it on Google Play