The Art of Inquiry: An In-Depth Conversation with Software Testing Visionary Michael Bolton
In the rapidly evolving landscape of software development, where the drive for automation often threatens to eclipse the necessity of human intellect, few voices carry as much weight as that of Michael Bolton. A distinguished software testing teacher, author, consultant, and industry thought leader, Bolton has spent decades challenging the status quo of Quality Assurance (QA).
As part of the SoftwareTestingHelp (STH) "Know The Leader" series, we sat down with Bolton to peel back the layers of his philosophy. This article explores his journey, his critique of modern certification culture, and his unwavering belief that testing is not a task, but a profound intellectual discipline.
The Genesis of a Tester: A Career Defined by Curiosity
To understand Michael Bolton’s approach to quality, one must first look at his origins. His path was not a linear trajectory designed in a classroom, but rather a cumulative experience of various professional roles.
"There are several ways to answer that question," Bolton reflects when asked about his beginnings. His entry into the world of software was organic, rooted in the technical landscape of the late 1980s and early 90s. From his early days editing a school newspaper to his hands-on experience in technical support starting in 1990, Bolton built a foundational understanding of how systems fail—and how users interact with them.
By 1994, he had officially stepped into a role titled "Software Tester" at Quarterdeck. However, he views this not as a starting point, but as a convergence of his experiences in writing code, supporting users, and analyzing text. For Bolton, software testing is the natural culmination of being a lifelong student of technology and business domains.
The Philosophy of "Rapid Software Testing"
One of Bolton’s most significant contributions to the industry is the development of the "Rapid Software Testing" (RST) methodology. When asked if his program is "one of a kind," Bolton offers a nuanced answer that separates his pedagogy from the rigid, exam-focused training common in the corporate world.
Beyond Memorization
Bolton argues that many professional certifications are designed merely to help candidates pass exams by memorizing terminology. In contrast, RST avoids exams entirely. "We don’t have exams," he notes. "We do suggest—quite strongly—that you think deeply about your own ideas about your craft, and how you talk about them."
The Classroom as a Laboratory
The power of the RST approach lies in its interactivity. Students do not just listen to lectures; they engage in live testing exercises, solve puzzles, and participate in collaborative retrospectives. By analyzing what went wrong and why, students move beyond rote execution and into the realm of true analytical testing. This focus on practical application is a sentiment shared by other industry luminaries, such as Rob Sabourin, whose "Just in Time Testing" classes similarly prioritize active, hands-on learning over passive theoretical instruction.
The Industry Crisis: Under-appreciation and Stagnation
Despite the critical nature of software testing in the digital age, Bolton observes a troubling trend: the systemic under-appreciation of testing teams.
A Low Standard of Practice
Bolton points to a dangerous cycle: employers frequently misunderstand the nature of testing, leading them to hold the discipline to a "low standard." Because leadership often fails to value the intellectual rigor required for high-quality testing, they prioritize speed and volume over insight.
This creates a vacuum where testers are discouraged from developing essential skills—such as systems thinking, critical analysis, and sophisticated reporting. When managers lack the expertise to distinguish between a "checker" (someone who runs scripts) and a "tester" (someone who explores, models, and evaluates), the entire quality lifecycle suffers.
The Great Debate: Tools, Process, or Critical Thinking?
A perennial question in the QA community is whether technical tool expertise is more important than soft-skill critical thinking. Bolton rejects this false dichotomy with a sharp analogy:
"That’s like asking, ‘What’s more important to being a successful bicycle rider—keeping your balance or steering?’ It’s not an either/or question."
Bolton emphasizes that while tools and process expertise provide the framework for efficiency, they are rendered impotent without the engine of critical thinking. A tool can only do what it is instructed to do; it cannot understand the context of the user or the subtle nuances of business risk. Therefore, successful testers must treat tools as extensions of their own analytical capabilities, not as replacements for them.
The Certification Trap
For aspiring testers looking to build their resumes, Bolton offers a word of caution regarding industry certifications. His stance is clear: "Most testing certifications don’t measure your ability to test."
Instead of chasing acronyms, he advises professionals to focus on deep, self-directed education. He recommends:
- Immersive Learning: Participating in classes like BBST (Black Box Software Testing).
- The Literature of Quality: Studying the works of pioneers like Gerald Weinberg, whose books provide the psychological and systemic foundation for high-quality testing.
- Active Community Engagement: Participating in groups like "Weekend Testing," where real-world problems are tackled in collaborative settings.
Looking Ahead: The Future of the Craft
The evolution of technology brings both threats and opportunities for the testing profession. Bolton warns of a future where "checking"—the rote, scripted execution of procedures—will be fully automated.
The Rise of "Checking" vs. "Testing"
"Sooner or later, people are going to realize that testing centered around confirmatory test cases is not very informative and not very valuable," Bolton warns. If a task can be reduced to a script, it is not testing; it is merely an algorithmic check.
Testers who fail to evolve beyond being "human scripts" risk obsolescence. However, those who master the art of investigation, experimental design, and analytical reporting will become more valuable than ever. The future belongs to the "expert tester" who can navigate the ambiguity that automation cannot touch.
The Core Skill: Telling the Testing Story
If there is one skill that distinguishes a senior, highly effective tester from a novice, it is the ability to "tell the testing story."
Bolton breaks this down into three essential "braids" that, when woven together, define a successful quality strategy:
- Product Status: Providing a clear, objective account of what the product does, what it doesn’t do, and how it fails in ways that matter to the stakeholders.
- The Testing Process: Explaining the methodology, the setup, the coverage, and the "oracles" used to make sense of the results. This is about transparency in how the tester arrived at their conclusions.
- The Quality of the Testing: A meta-analysis of the testing itself. Why was this the best approach? What obstacles were encountered? What is needed to improve testability in future cycles?
By mastering this narrative, a tester transitions from being a "bug reporter" to a "quality consultant."
Final Thoughts: A Call to Continuous Growth
In closing, Bolton resists the urge to name a single "magic bullet" skill for success. Instead, he advocates for a life of continuous, context-driven inquiry.
"Follow critical thinking; when you see or think about something, ask ‘what else could this be?’" he advises.
Michael Bolton’s career serves as a testament to the idea that testing is an intellectual profession. As the software industry continues its relentless march toward automation, his message remains a beacon for those who choose to pursue the craft with rigor, passion, and a persistent curiosity. For the modern tester, the mandate is clear: keep learning, keep questioning, and above all, keep telling the story of your work.
