Inside the Mind of a Software Testing Pioneer: An Exclusive Interview with Michael Bolton

By the Editorial Team
SoftwareTestingHelp (STH)

Main Facts

In the rapidly evolving landscape of software development, where automation and artificial intelligence increasingly dominate headlines, the foundational philosophies of software testing often risk being overshadowed. To recalibrate the industry’s compass, SoftwareTestingHelp (STH) sat down with renowned software testing teacher, author, consultant, and thought leader Michael Bolton.

Part of the ongoing "Know The Leader" interview series—following previous high-profile discussions with leaders like Neeraj Tripathi, VP of Global QA at Infor—this comprehensive dialogue dives deep into Bolton’s philosophy on the craft of testing. Key takeaways from the interview include:

• The Evolution of a Tester: Bolton’s entry into the field was non-traditional, spanning technical support, software writing, and journalism before landing a formal testing role at Quarterdeck in 1994.
• The Myth of Certification: Bolton argues that standard certifications fail to measure real testing ability, advising professionals to focus on self-education, foundational literature, and deep-dive training programs like Rapid Software Testing (RST) and BBST.
• Critical Thinking Over Tools: Testing cannot be reduced to a binary choice between tools or critical thinking; rather, tools are merely supplementary to deep analytical and systems thinking.
• The Threat of "Checking": Rote script-execution—which Bolton terms "checking"—is increasingly vulnerable to automation, threatening testers who fail to evolve into analytical investigators.
• The Power of the Testing Story: The ultimate differentiator for a successful tester is the ability to articulate a comprehensive, three-stranded testing narrative covering the product, the methodology, and the quality of the testing process itself.

Chronology: A Career Forged Across Decades

To understand Michael Bolton’s pragmatic and uncompromising approach to quality assurance, one must look at the timeline of experiences that shaped his career. Long before he became a globally recognized consultant and co-creator of Rapid Software Testing (alongside James Bach), Bolton’s trajectory was built on a foundation of diverse technical and communicative roles.

• Pre-1988 (The Foundational Years): Bolton’s early training in communication began during his time editing his school newspaper—an experience he credits with teaching him how to investigate, synthesize, and report on complex narratives.
• 1988 (Writing Software): Bolton took his first steps into software creation, gaining a developer’s perspective on how code is structured, written, and inevitably prone to failure.
• 1990 (Technical Support): Stepping into tech support forced Bolton to confront how real-world users interact with software, exposing the gap between intended design and actual user experience. This direct exposure to customer frustration and product bugs laid the groundwork for diagnostic testing.
• 1994 (Entering the Profession): Armed with cross-disciplinary insights from journalism, coding, and support, Bolton officially stepped into the software industry with the title of "software tester" at Quarterdeck.
• Present Day: Today, Bolton operates as a premier educator, traveling the world to teach Rapid Software Testing, consult with enterprise development teams, and challenge the status quo of modern QA practices.

Supporting Data and Industry Context

The state of software testing is at a critical crossroads. Industry reports frequently highlight the tension between manual exploratory testing and automated regression testing. Bolton’s insights address several systemic issues plaguing contemporary development pipelines:

The Skills Gap and Managerial Misunderstanding

According to Bolton, the single biggest challenge facing testing teams is a widespread organizational misunderstanding of what testing actually is. When management views testing as a mere bureaucratic hurdle or a repetitive checklist, it creates a race to the bottom. Unskilled managers hire unskilled testers, creating an echo chamber that devalues the profession.

The Fallacy of Memorization-Based Certifications

While thousands of testers spend time and money pursuing traditional certifications, industry veterans frequently caution against treating these credentials as proof of competence. Bolton points out that standard multiple-choice exams measure one’s ability to memorize terminology rather than the ability to discover critical bugs under pressure. Instead, he directs aspiring professionals toward interactive, practice-heavy programs like:

• Rapid Software Testing (RST) and RST Applied
• Rob Sabourin’s Just in Time Testing classes
• Black Box Software Testing (BBST) courses
• The timeless writings of Gerald M. ("Jerry") Weinberg

Official Responses and Perspectives

During the STH interview, Bolton addressed several core dilemmas faced by modern testing professionals. Below is a thematic breakdown of his expert perspectives.

On the Purpose of Rapid Software Testing

Addressing whether RST is one of a kind, Bolton explained that while interactive testing exercises exist in other advanced curricula—such as those by Rob Sabourin and the BBST series—RST stands apart by rejecting rote memorization.

"We do suggest—quite strongly—that you think deeply about your own ideas about your craft, and how you talk about them. And that you talk about your craft with other people. That’s what experts do."

On Tools vs. Critical Thinking

When asked whether analytical thinking or tool expertise takes precedence, Bolton rejected the false dichotomy:

"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. Tools and process expertise aren’t very reliable or useful in the absence of analysis and critical thinking."

On the Evolution (and Danger) of Automated "Checking"

Bolton drew a sharp line between testing (an open-ended process of discovery and evaluation) and checking (the algorithmic execution of predetermined scripts):

"When that kind of work can be done by algorithms, by computer programs, we call that ‘checking’… Testers who are presently following other people’s instructions have the option of upgrading their programming skills, or their analytical skills, or their social-science skills, or looking for other jobs."

Implications for the Future of Quality Assurance

Bolton’s insights carry profound implications for software engineering organizations and individual QA practitioners alike.

1. The Redefinition of the Tester’s Role

As continuous integration and automated testing frameworks absorb routine verification tasks, human testers can no longer rely on script-following to secure their employment. The future belongs to "testers who are experts in testing, in analyzing, in designing, and in performing experiments." Those who fail to evolve into critical investigators face displacement.

2. The Art of the Testing Story

Perhaps Bolton’s most actionable advice for practitioners is mastering the skill of telling the testing story. He breaks this crucial narrative down into three interconnected strands:

1. The Product Status: What the software does, what it fails to do, and how it might fail in ways that matter to stakeholders.
2. The Methodology and Coverage: How the product was tested, the environments set up, the oracles applied, and what areas remain unexamined.
3. The Quality of Testing: An evaluation of the testing process itself—identifying what made testing harder or slower, the presence or absence of testability features, and recommendations to accelerate deep discovery.

3. Democratization of Testing Skills

Looking toward future trends, Bolton expresses a hopeful vision: testing should not be viewed as an isolated silo, but rather as a core set of skills that pervades the entire software development lifecycle. When developers, designers, and business analysts adopt testing mindsets, product quality rises exponentially—leaving specialized testers to act as collaborative anchors rather than gatekeepers.

Conclusion

Michael Bolton’s interview with SoftwareTestingHelp serves as both a reality check and an inspiring manifesto for the software testing community. By stripping away corporate bureaucracy and emphasizing deep critical thinking, empirical experimentation, and narrative prowess, Bolton charts a clear path forward for professionals dedicated to mastering their craft.

For more insights from the industry’s most influential figures, stay tuned to SoftwareTestingHelp’s "Know The Leader" series. You can follow Michael Bolton’s ongoing work and writings via his DevelopSense Blog and on Twitter.