Beyond the Script: An In-Depth Conversation with Software Testing Visionary Michael Bolton
In the rapidly evolving landscape of software development, where automation and artificial intelligence are constantly redefining the boundaries of quality assurance, few voices carry as much weight as that of Michael Bolton. A software testing teacher, consultant, author, and preeminent thought leader, Bolton has spent decades challenging the industry to look beyond rote execution and embrace the intellectual rigor of true investigation.
As part of the "Know The Leader" series, Software Testing Help sat down with Bolton to dissect the current state of software testing, the philosophical divide between "checking" and "testing," and the imperative for testers to evolve or risk obsolescence.
The Genesis of a Testing Philosophy: A Chronology of Expertise
To understand Michael Bolton’s approach to quality, one must understand his trajectory. His career does not follow a linear path of certifications and standard milestones; rather, it is a mosaic of experiences that built a foundation for critical thinking.
Bolton’s journey began long before he held the official title of "software tester." He traces his analytical roots back to his days editing his school newspaper—a role that demanded an eye for detail and a commitment to clarity. By 1988, he was writing software, and by 1990, he had transitioned into technical support. These roles were not just stepping stones; they were the "university" of his career.
"The experience and skills that I developed in all these situations contributed to making me qualified for a job called ‘software tester,’" Bolton notes. It wasn’t until 1994, at Quarterdeck, that he formally occupied that role. This background is critical because it frames his view of testing: it is not a siloed task, but a holistic discipline that integrates development, support, and communication.
Supporting Data: Why "Rapid Software Testing" Resonates
Bolton is perhaps best known for his work in "Rapid Software Testing" (RST). In an industry saturated with rigid certification programs that focus on terminology and exam preparation, RST stands out for its lack of exams and its focus on cognitive flexibility.
The Problem with "Checklist" Testing
Bolton argues that the industry’s obsession with credentials often masks a lack of genuine skill. "Lots of classes focus on memorizing terminology so that you can pass an exam," he explains. "The terminology is not unimportant—we think words are very important because they help us think about things in sharper ways—but we don’t insist that you use our words."
Instead, RST emphasizes:
- Active Engagement: Working on puzzles and testing actual software in real-time.
- Collaborative Discourse: Discussing what happened and what was learned rather than adhering to a predetermined script.
- Expert Practice: Modeling the behavior of experts, which involves deep thinking and open discussion about one’s craft.
According to industry observers, this shift toward "practice-based learning" is becoming increasingly vital. While other programs like Rob Sabourin’s "Just in Time Testing" or the BBST (Black Box Software Testing) series also emphasize interactive exercises, the common thread is clear: testing is a craft that requires constant application, not just passive absorption of theories.
Official Responses: Addressing the Industry’s "Under-Appreciation"
A recurring theme in the interview is the perception of testing teams as "under-appreciated" entities within the software development lifecycle. Bolton is characteristically candid about why this exists.
"The biggest challenge that I see is that employers misunderstand testing, and therefore hold it to a low standard," Bolton states. This creates a feedback loop of mediocrity. If managers do not understand what testing is, they hire based on outdated criteria, and if the testers they hire fail to develop their own critical thinking and technical skills, the entire discipline suffers.
The "Bicycle" Analogy
When asked about the relative importance of analytical thinking versus tool/process expertise, Bolton rejects the false dichotomy. He draws an analogy to riding a bicycle: "What’s more important to being a successful bicycle rider—keeping your balance or steering? It’s not an either/or question."
Tools and processes are merely instruments. Without the analytical framework provided by critical thinking, they are useless. Conversely, deep analysis can be accelerated and amplified by the intelligent use of tools. A successful tester must be able to harmonize both.
The Great Divide: "Testing" vs. "Checking"
One of the most profound implications in Bolton’s work is the distinction between testing and checking.
- Checking: The act of confirming that the product behaves in a specific way using a script. Because this is algorithmic and repetitive, it is the type of work that can be easily delegated to machines and automated scripts.
- Testing: The intellectual, investigative process of learning about the product, uncovering risks, and understanding how it might fail in ways that actually matter to the end user.
Bolton warns that the future is bleak for those who view testing as mere "bureaucracy and paperwork." He observes that many organizations still prioritize the rote execution of test procedures. "Sooner or later," he warns, "people are going to realize that testing centered around confirmatory test cases is not very informative and not very valuable."
For those currently stuck in the "instruction-following" phase of their career, the choice is stark: either upgrade your skills in programming, systems thinking, and social science, or face displacement by automation.
Implications: The Future of the Testing Profession
Looking toward the horizon, Bolton remains optimistic, albeit with a caveat. He envisions a future where testing is recognized as a fundamental skill that permeates all aspects of software development—not just something done by a "QA person" at the end of the line.
"My hope is that testing will be recognized as a key set of skills that pervades all of software development," he says. However, for this to occur, the "testing literacy" of the entire development team—including designers and business stakeholders—must be raised.
The Art of the Testing Story
If there is a singular piece of advice Bolton offers to the next generation, it is the mastery of the "testing story." A tester who cannot articulate their findings is, in his view, a tester who cannot be effective. He breaks this down into three essential "braids":
- Product Status: A clear narrative about what the product does, what it doesn’t do, and how it fails in ways that impact the user.
- The Testing Process: A transparent account of how the testing was conducted, the oracles used, and the scope of coverage—including what was not tested and why.
- The Quality of Testing: A reflection on the constraints of the testing effort, the testability of the product, and recommendations for improvement.
Conclusion: A Call to Action for Aspiring Testers
For those seeking to become successful in this field, Bolton advises against looking for a "magic bullet" skill. Instead, he encourages a mindset of perpetual curiosity.
"Practice what is most helpful to you in your current context, and practice stuff that interests you," he suggests. He encourages testers to cultivate a healthy skepticism by constantly asking, "What else could this be?"
The era of the "script-follower" is drawing to a close. As Michael Bolton’s career exemplifies, the future belongs to the investigators—those who treat software testing not as a series of chores to be completed, but as a dynamic, intellectual, and storytelling-driven profession. For those willing to embrace this, the "university" of software testing remains open, and the opportunities for growth are limited only by the depth of one’s own curiosity.
For more insights on the craft of software testing, readers are encouraged to follow Michael Bolton on Twitter and explore his extensive archives at DevelopSense.
