Teaching software testing to children through fantasy storytelling uses dragons as defects and knights as testers, building a complete analogy around software quality concepts. Each chapter covers a different quality attribute, such as functional behavior, performance, usability, or security, with text boxes translating story events into testing terms. The approach targets readers from age nine to ninety-nine.
Key Takeaways
- Dragons as defects and knights as testers form the central analogy of the book, with every character, from villagers to lords, mapped to a role in software quality.
- The book covers quality attributes chapter by chapter, using James Bach’s heuristic bug taxonomy as a structural checklist to ensure defect types are not missed.
- Four iterative feedback rounds with children, teachers, testing professionals, and non-IT adults shaped the story, each round using new readers to get unbiased reactions.
- The book was donated to roughly fifty schools in Finland, with ISTQB boards in other countries running parallel donation campaigns to local schools.
- A planned second volume would cover testing techniques, heuristics, test automation, and AI, extending beyond the quality-characteristics focus of the first book.
Why testing needs its own children’s book
There are plenty of books about software testing for professionals, but almost nothing that explains testing to children. That gap is what Kari Kakkonen set out to close. The book teaches software testing through a fantasy world where dragons stand for defects and knights stand for testers and developers.
The reasoning is simple. Coding shows up in school curricula, testing rarely does. In Finland, for example, the government curriculum requires teachers to cover coding all the way from elementary school up to high school. Testing is not part of that mandate.
Kari saw an opening. Once you accept that software has to be tested and not just written, testing belongs in the same conversation as coding. A story aimed at children can carry that idea into classrooms where it otherwise never appears.
How the dragon analogy holds the whole world together
The core analogy is that dragons are defects and knights are the people who find or tame them. Around that single mapping, Kari built a complete fantasy world where every element corresponds to something in the testing domain.
He tested the idea before committing to it. Dragons as good guys or bad guys did not work when he tried it out verbally with children. Dragons as defects did. From there, the rest fell into place: different kinds of dragons for different kinds of defects, different knights for testers with different skills, plus villagers, lords, and ladies who all have a role in ensuring quality.
The book maps directly onto the ISTQB world. Anything a reader sees in the story is an analogy for a real testing concept. That makes the fantasy more than decoration, it is a teaching structure.
What the storyline actually does
Two children, a girl and a boy, drive the narrative. They notice strange things happening, encounter dragons, and meet a knight. Their enthusiasm grows, and they decide to help find dragons and get rid of them, or even befriend them so the dragons cause no harm.
The story keeps the two children present throughout. That continuity was a deliberate fix. In the original draft, the chapters were more separate, and a few of them had to be reworked so the same two characters carry the reader from start to finish.
Roughly once per page, a text box interrupts the story to explain what just happened. A green dragon turns out to be a usability defect, handled by a knight with a particular skill set. The mechanism is spelled out plainly, so a young reader understands the lesson behind the scene.
The book is organized by quality attributes
Each chapter covers a different quality attribute or type of defect. There is a functional chapter, a performance chapter, a usability chapter, a security chapter, and so on.
Kari used Cem Kaner’s bug taxonomy as a checklist. He worked through the categories one by one, confirming each was covered before moving to the next chapter. Most of the defects in that classification made it into the book.
Some topics were left out on purpose. Test automation and AI are only hinted at, not explained in depth. That is room reserved for a follow-up.
Why an intro book can reach professionals too
The book works for ages nine to ninety-nine, and adults are part of the intended audience. Parents read it to explain testing to their kids. Teachers use it to bring IT, coding, and testing into their classes. Testing professionals read it for themselves.
For professional readers, the value sits in what is not spelled out. Kari deliberately carried the analogy further than the text boxes explain, leaving small connections for the reader to find.
There is a black dragon. I don’t explain why the dragon is black. So you can try to find the analogy and think why is it black. — Kari Kakkonen
That open question is the exercise. A professional who already knows the field can read the same story a child reads and decode the layer underneath.
How iterative feedback shaped the writing
Kari wrote the book the way a tester would build it: in rounds, with fresh readers each time. He ran four feedback rounds, covering the first chapter, one third of the book, two thirds, and the full manuscript.
Using a new person for each round was the point.
It’s like tissue testing these days. You need to have a new person to try out the same ideas. — Kari Kakkonen
He gathered reactions from a wide mix: teachers, testing professionals, non-IT people, and children of different ages. The feedback confirmed the direction and prompted concrete changes, the biggest being the move to a single continuous storyline.
Children give honest feedback, sometimes blunt. One reader will call a passage boring. Another lights up. At a book fair, a roughly twelve-year-old girl looked at the back cover, leafed through a little, and told her mother she wanted to buy it because it looked interesting enough that she wanted testing as a profession. A strong first impression from a few minutes with the cover.
Getting the book into schools through donations
The book exists in five languages: Finnish, English, French, German, and Polish. The English and Finnish editions came out at roughly the same time, and that timing opened a path into schools.
Kari ran a donation campaign alongside the English release. Companies and associations, including many ISTQB boards, pre-ordered books that were then donated to local schools once the editions were available.
In Finland, he handled the distribution himself and donated books to about fifty schools. In other countries, the local ISTQB boards did the same for schools in their regions. The campaign reached its high point when he handed a certificate of donations to Finland’s Minister of Education, along with a copy of the book.
What a second book would add
A follow-up would move past defect types into techniques and heuristics. The current book mostly explains testing types: a quality characteristic and the testing type that goes with it. The next step is the how.
A chapter on security testing techniques is one example, showing how you actually find security defects rather than just naming the category. Alongside that, Kari names test automation and AI as the topics he held back from the first book.
The illustration style was chosen with this future in mind. Kari hired an illustrator and pushed through several iterations toward a simple, clear look for the dragons. The aim was characters that could later work as 3D figures in a movie or cartoon if the book takes off. Simple by design, not by accident.
