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 for human intuition, few voices remain as steadfast and influential as that of Michael Bolton. As a renowned software testing teacher, author, and consultant, Bolton has spent decades challenging the industry’s status quo.
In this exclusive interview, part of the SoftwareTestingHelp "Know The Leader" series, we delve into the philosophy, challenges, and future trajectory of software testing. Bolton’s approach, rooted in the principles of "Rapid Software Testing" (RST), serves as a masterclass in critical thinking for professionals navigating the complexities of modern engineering.
The Genesis of an Expert: A Professional Chronology
Michael Bolton’s journey into the heart of software testing was not a linear path, but rather a convergence of diverse technical disciplines. When asked about the origins of his career, Bolton reframes the question, noting that his expertise was forged in the fires of various roles.
"I could say that I became a software tester when I started editing the school newspaper, but that is too long ago to mention," he quips. His formal entry into the field, however, is marked by a steady progression: writing software in 1988, transitioning into technical support in 1990, and finally securing the title of "Software Tester" at Quarterdeck in 1994.
This chronology is vital to understanding his methodology. Bolton views testing not as a siloed task, but as a culmination of skills—technical acumen, writing, and support—that allow a tester to act as a bridge between the product’s architecture and the end-user’s experience. For him, testing is a lifelong university, where the curriculum is the product itself and the classroom is the entire career.
Rapid Software Testing: Beyond the Syllabus
One of the most frequent points of discussion in the testing community is the efficacy of training programs. Bolton’s own program, Rapid Software Testing (RST), is often cited as a gold standard, yet he is quick to demystify its "one-of-a-kind" status.
A Philosophy of Practice over Pedagogy
Bolton distinguishes his approach from traditional certification-heavy courses that prioritize rote memorization. "Lots of classes focus on memorizing terminology so that you can pass an exam," he observes. "We don’t have exams." Instead, RST focuses on developing a vocabulary that sharpens one’s thinking, rather than mandating a specific, rigid lexicon.
The core of his pedagogy is interactivity. Participants in RST—and similarly rigorous programs like Rob Sabourin’s "Just in Time Testing" or the BBST series—engage in live testing exercises and puzzles. This focus on "doing" rather than "listening" reflects a core tenet of Bolton’s philosophy: testing is a craft that requires constant practice.
The State of the Industry: Challenges and Misconceptions
The perception of testing teams as "under-appreciated" is a pervasive sentiment in the software industry. Bolton identifies a structural failure in how organizations value the testing function.
The Low-Standard Trap
"The biggest challenge that I see is that employers misunderstand testing, and therefore hold it to a low standard," Bolton explains. This creates a cycle of mediocrity: when management views testing as a low-skill, administrative task, they hire accordingly. If the testers themselves do not prioritize self-development in critical thinking, systems thinking, and technical reporting, the industry stagnates.
The Myth of "Either/Or" Expertise
Bolton vehemently rejects the false dichotomy between "analytical/critical thinking" and "tool/process expertise." He compares this to asking a cyclist whether "balance" or "steering" is more important.
"Tools and process expertise aren’t very reliable or useful in the absence of analysis and critical thinking," he notes. Conversely, the most powerful analytical mind is limited if it lacks the technical tools to execute experiments. The successful tester, in Bolton’s view, is the one who seamlessly integrates both.
Official Stance: The Certification Debate
When questioned about the value of industry certifications, Bolton offers a candid, often provocative, perspective. He advises aspiring professionals to look beyond the certificate.
"Most testing certifications don’t measure your ability to test," he asserts. His recommendation is to focus on genuine education—reading the foundational works of figures like Jerry Weinberg, engaging with community-driven initiatives like Weekend Testing, and participating in courses that demand practical application.
For Bolton, professional growth is an organic process. It is built through reading, debating with peers, and, most importantly, testing real-world software until the logic behind the bugs becomes clear.
Implications: The Future of the Tester
Perhaps the most pressing question for the modern tester is the threat posed by the rise of automation and artificial intelligence. Bolton offers a nuanced, if cautionary, forecast.
Checking vs. Testing
Bolton makes a vital distinction between "checking" and "testing."
- Checking: The rote execution of procedures, looking for specific outputs based on specific inputs. This is highly algorithmic and, in many cases, can be offloaded to machines.
- Testing: The intellectual pursuit of uncovering the unknown—the "what if" scenarios that an algorithm cannot predict.
"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. Testers who view their role as merely following a pre-written script are at high risk of displacement. However, those who master the art of investigation, experimental design, and analytical reporting will not only survive but become indispensable to the development lifecycle.
Strategic Advice: The Skill of Storytelling
If there is a secret weapon in the arsenal of a great tester, it is the ability to tell the "testing story." Bolton breaks this down into three essential, intertwined threads:
- The Product Story: A clear, honest assessment of what the product does, what it fails to do, and the risks it poses to the end-user.
- The Process Story: A detailed account of how the testing was conducted, what was covered, and—crucially—what was not covered.
- The Quality Story: An evaluation of the testing itself. Did the constraints of the environment hinder the process? How could the product’s testability be improved?
By mastering these threads, a tester transitions from a "bug hunter" to a strategic partner who provides stakeholders with the data they need to make high-level decisions.
Conclusion: A Call to Continuous Growth
In closing, when asked for a singular skill that every tester should focus on, Bolton remains characteristically pragmatic. There is no "silver bullet." Instead, he advocates for a mindset of constant, aggressive curiosity.
"Follow critical thinking; when you see or think about something, ask ‘what else could this be?’"
Michael Bolton’s career serves as a testament to the idea that software testing is a high-stakes, intellectual pursuit. By eschewing the comforts of rote instruction and embracing the discomfort of deep, analytical inquiry, testers can transform their roles from a project afterthought into the primary safeguard of quality. As the industry advances, the testers who will thrive are those who—like Bolton—treat every bug as a lesson and every product as a puzzle waiting to be solved.
