In an industry defined by rapid iteration, evolving methodologies, and the constant threat of technical obsolescence, few voices carry as much weight as that of Michael Bolton. As a celebrated software testing teacher, author, consultant, and 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 dissect the philosophy of his work, the shifting landscape of testing, and the critical skills required to survive in an era dominated by automation and algorithmic decision-making.
The Genesis of a Tester: A Professional Chronology
To understand Michael Bolton’s approach, one must understand his origins. Unlike those who follow a linear path toward a specific certification, Bolton’s career is a tapestry of roles that collectively formed his testing methodology.
"I could say that I became a software tester when I started editing the school newspaper," Bolton recalls, noting that the analytical rigor of journalism parallels the detective work required in QA. His journey continued through technical roles starting in 1988 as a software developer, followed by a tenure in technical support in 1990.
These roles provided a foundational understanding of the software lifecycle—from the frustration of end-users to the complexities of code architecture. By 1994, when he was officially hired as a "Software Tester" at Quarterdeck, he was already equipped with a holistic view of the ecosystem. For Bolton, testing is not merely a department; it is a "university" that lasts a professional’s entire career, offering the unique privilege of being paid to learn technology, business domains, and complex problem-solving.
Rapid Software Testing: Beyond the Exam Room
A major pillar of Bolton’s professional output is his Rapid Software Testing (RST) program. In a market saturated with standardized certifications, RST stands out by rejecting the traditional "memorize and test" model.
The Philosophy of Non-Standardization
Bolton is a vocal critic of the testing industry’s obsession with rote terminology and exam-based certification. "Lots of classes focus on memorizing terminology so that you can pass an exam," he explains. "We don’t have exams." Instead, RST focuses on cognitive development. Bolton believes that while vocabulary is essential for "thinking in sharper ways," he does not insist on a rigid lexicon.
The core of the RST philosophy is peer-to-peer interaction. Students work on puzzles and real-world software, engaging in discourse about the process. By emphasizing practice over theory, Bolton aligns his methodology with other high-level training programs like the BBST (Black Box Software Testing) courses and the "Just in Time" testing classes pioneered by figures like Rob Sabourin.
Industry Challenges: The Myth of the Under-Appreciated Tester
A recurring theme in the interview is the perception of testing teams as under-appreciated entities within software development projects. According to Bolton, this is not a symptom of the industry’s lack of respect, but rather a lack of competence in leadership.
The Cycle of Unskilled Management
"The biggest challenge that I see is that employers misunderstand testing, and therefore hold it to a low standard," Bolton asserts. This creates a dangerous feedback loop:
- Low Standards: Management views testing as a clerical, "check-the-box" activity.
- Skill Stagnation: Testers, discouraged by the lack of intellectual demand, fail to develop critical thinking or advanced technical skills.
- Amplification: The resulting low-quality testing reinforces management’s belief that the role is secondary, leading to even lower investment.
Bolton argues that breaking this cycle requires a radical shift. Testers must move beyond simple script execution and demonstrate value through sophisticated analysis and systems thinking.
The Analytical Divide: Critical Thinking vs. Technical Expertise
One of the most common questions posed to industry veterans is whether a tester should prioritize analytical skills or technical tool expertise. Bolton rejects this false dichotomy entirely, likening it to asking a cyclist whether they should prioritize "keeping their balance" or "steering."
"It’s not an either/or question," he clarifies. In his view, tool expertise is essentially useless without the analytical capacity to interpret the output. Conversely, critical thinking is significantly amplified when supported by the right technical tools. A successful tester, therefore, must operate at the intersection of both—using tools to expedite data gathering, while using human intellect to decide what that data actually signifies.
The Future of Testing: "Checking" vs. "Testing"
Perhaps the most provocative portion of the conversation involves the future of the profession. Bolton distinguishes sharply between "checking"—the algorithmic, repetitive validation of expected outcomes—and "testing," which is the intellectual process of exploring and understanding a product.
The Looming Risk of Automation
Bolton warns that testers who rely solely on following instructions are at high risk of being replaced by machines. "When that kind of work [repetitive execution] can be done by algorithms, we call that ‘checking,’" he says.
As organizations realize that confirmatory test cases provide limited value, the roles of those who simply execute scripts will diminish. However, he sees a bright future for those who evolve. Testers who master programming, social science, and advanced analytics will become the architects of quality, while those who remain "button-pushers" will find themselves obsolete.
The Art of the Testing Story
When asked for the single most important piece of advice for upcoming testers, Bolton pivots to a skill that is rarely taught in technical bootcamps: The art of storytelling.
A tester’s value is only as good as their ability to communicate it. Bolton breaks this down into a "braid" of three essential narrative strands:
- The Product Status: A clear explanation of what the product does, what it doesn’t do, and how it fails in ways that matter to stakeholders.
- The Testing Methodology: A transparent account of how the product was tested, the oracles applied, and the scope of coverage—including what was not tested and why.
- The Quality of the Testing: A meta-analysis of the testing process itself. This includes an assessment of testability, recommendations for improvement, and an honest evaluation of why the testing was the best possible under the given constraints.
Conclusion: A Call for Continuous Evolution
Michael Bolton’s outlook is one of cautious optimism. He envisions a future where testing is recognized as a pervasive skill set that belongs to everyone—designers, developers, and business analysts alike. Yet, for this to occur, the global community of testers must commit to a higher standard of professional practice.
There is no "silver bullet" skill. Instead, Bolton encourages a lifestyle of constant intellectual curiosity. Whether it is reading the works of Jerry Weinberg, engaging with communities like Weekend Testing, or simply asking "what else could this be?" when analyzing a system, the path to success is paved with self-directed education.
As software grows more complex and the pace of delivery accelerates, the role of the human tester becomes not less relevant, but more critical. By moving beyond the manual execution of scripts and embracing the complexity of systems thinking, the next generation of testers can transform from "the under-appreciated team" into the most vital asset in the software development lifecycle.