← Latest papers
💻 computer science

Teaching testing seriously in academia

This position paper argues that software testing education should shift from a rationalist, prescriptive paradigm to an empirical, inquiry-driven approach, proposing the P4TEST framework and 4C/ID instructional model to better equip students with the critical reasoning skills needed for complex, AI-integrated systems.

Original authors: Tanja E. J. Vos, Bart Th. Knaack, Beatriz Marín, Niels Doorn, Nikè van Vugt-Hage

Published 2026-06-16
📖 4 min read☕ Coffee break read

Original authors: Tanja E. J. Vos, Bart Th. Knaack, Beatriz Marín, Niels Doorn, Nikè van Vugt-Hage

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are teaching someone how to be a detective.

The Problem: Teaching the Wrong Kind of Detective
Right now, universities are teaching software testing like a math class. They give students a clear list of rules (the "specification"), a specific puzzle to solve, and a single correct answer. If the student follows the steps and finds the answer, they get an A.

The authors argue this is the wrong way to teach testing. Real-world software (especially with AI) is messy, unpredictable, and often has no clear rulebook. By teaching students to just "check the boxes" and confirm what they expect to happen, we are training them to be proof-readers, not investigators. When they graduate and face a system that behaves strangely, they get frustrated because they were never taught how to ask, "What if this goes wrong?" or "What did I miss?"

The Solution: The "Whole Task" Approach
The paper suggests we need to change the paradigm from "Rationalism" (following a recipe) to "Empiricism" (exploring the unknown). To do this, they propose a new teaching framework called P4TEST, built on a learning model called 4C/ID.

Think of 4C/ID not as a ladder where you climb one rung at a time, but as a flight simulator. You don't start by learning how to tighten a single bolt in a garage. You start by sitting in the cockpit, looking at the whole plane, and learning how to fly it, even if you crash a few times at first.

How P4TEST Works: The Detective's Toolkit
P4TEST breaks testing down into a cycle of four main activities, like a detective solving a case:

  1. Modelling: Drawing a map of what you think the system is (even if the map is wrong).
  2. Investigation: Going out and gathering evidence (testing the software).
  3. Sensemaking: Figuring out what the evidence means. Did the software break? Why?
  4. Reflection: Changing your map based on what you found and trying again.

The Four Levels of Training (The Flight Simulator Levels)
The paper outlines four stages to take a student from a beginner to a pro:

  • Level 1 (The Case Study): Students don't test anything yet. They watch a "master detective" (an experienced tester) investigate a simple object, like a pen. They watch how the expert asks questions, changes their mind, and finds hidden flaws. It's like watching a cooking show before you ever touch a knife.
  • Level 2 (The Guided Practice): Students test a simple, small program (like a random number generator). They are given a map and a compass (tools and hints) to help them find the bugs. The teacher is right there, guiding them.
  • Level 3 (The Complex Mission): Students test a more complicated system (like a cash register). The teacher steps back. The students have to choose their own maps and decide which tools to use. They have to handle more confusion on their own.
  • Level 4 (The Real Job): Students do a real-world testing project. There is no map, no compass, and no teacher holding their hand. They must figure out what to test, how to test it, and explain their findings to a client.

The Secret Sauce: Habits of Mind
The paper emphasizes that you can't just teach the steps; you have to teach the mindset. They call these "Habits of Mind":

  • Disciplined Skepticism: Don't trust the results just because they look right. Ask, "Is this a trick?"
  • Epistemic Openness: Be willing to change your mind when new evidence appears.
  • Tolerance for the Unknown: Don't panic when you don't have all the answers. Use the confusion as fuel to keep investigating.
  • Deliberate Curiosity: Don't stop just because you found one bug. Ask, "What else could break?"

How to Test the Students
Finally, the paper argues that you can't test these skills with a multiple-choice exam. You can't ask, "What is the definition of a bug?" and expect to know if someone is a good tester.

Instead, they propose video-based assessment. Students record themselves testing software while talking out loud (like a "think-aloud" commentary). Teachers watch the video to see how the student thinks, how they handle confusion, and how they change their strategy when things go wrong. It's like a medical school where they watch a student perform surgery, rather than just grading a written paper about surgery.

In Summary
This paper is a call to stop treating software testing like a math problem with one right answer. Instead, it should be taught as a complex, investigative skill where the goal is to explore the unknown, embrace uncertainty, and learn how to think critically when the rules don't exist.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →