Mastering the Craft of Quality: An In-Depth Interview with Software Testing Thought Leader Michael Bolton
In an industry perpetually racing toward automated efficiency and rapid deployment, the fundamental definition of software testing is undergoing a profound identity crisis. Amidst the noise of certification mills and script-driven execution, few voices advocate as passionately for deep critical thinking, human analysis, and exploratory mastery as Michael Bolton.
As part of the ongoing "Know The Leader" interview series by SoftwareTestingHelp (STH)—following previous high-profile conversations with industry leaders like Neeraj Tripathi, VP of Global QA at Infor—STH recently sat down with Michael Bolton. A renowned software testing teacher, author, consultant, and creator of Rapid Software Testing (RST), Bolton offered a masterclass in how modern testers can elevate their craft, survive industry disruptions, and reclaim their value in software development.
Main Facts: The State of Modern Software Testing
Bolton’s dialogue with STH centers on a stark reality check for the QA industry: traditional software testing is undervalued because it is widely misunderstood. When organizations view testing merely as a bureaucratic compliance check—executing pre-written scripts and logging binary pass/fail results—they reduce human testers to mechanical cogs. Bolton distinguishes this rote work as "checking," which can increasingly be handled by algorithms and automation.
True testing, by contrast, is an exploratory, highly cognitive investigation. According to Bolton, the greatest threats to modern testing teams are:
- Misunderstanding from Leadership: Organizations holding testing to low standards because leadership lacks testing literacy.
- Skill Stagnation: Testers failing to develop critical thinking, systems thinking, and technical reporting skills.
- Over-Reliance on Certifications: The false security offered by traditional testing certifications that measure rote memorization rather than actual testing capability.
Conversely, Bolton highlights the immense upside of the profession: testing serves as an intellectual university where practitioners continuously learn about technology, business domains, and human problem-solving, and get paid to do it.
Chronology: From Journalism and Coding to Testing Leadership
Bolton’s path to becoming a recognized pillar of the software testing community was shaped by a diverse, multidisciplinary background rather than a linear academic track in QA.
- Early Beginnings: Bolton traces his foundational exposure to testing back to editing his school newspaper and utilizing various early software systems.
- 1988: He began writing software, gaining an appreciation for how code is constructed from the ground up.
- 1990: He entered technical support, sharpening his ability to diagnose user pain points and investigate system failures.
- 1994: All these overlapping experiences coalesced when he was officially offered a job with the title "software tester" at Quarterdeck.
This multifaceted background cemented his lifelong philosophy: successful testing cannot be neatly separated from critical thinking, technical empathy, and strong communication. Today, through his consultancy DevelopSense and educational programs like Rapid Software Testing, Bolton travels the globe teaching these exact holistic principles.
Supporting Data and Industry Insights: The Anatomy of Bolton’s Philosophy
The interview sheds light on several core debates within the software engineering community, offering sharp perspectives on training, tooling, and industry trends.
The Myth of Certifications vs. Real Education
When asked whether certifications help testers improve, Bolton pulls no punches. Most testing certifications, he notes, fail to measure an individual’s actual ability to test. Rather than chasing acronyms or exam credentials, aspiring testers are urged to invest their energy in self-education. Bolton recommends diving into the Bug Bashem / Context-Driven School of Testing (BBST) class materials, reading the foundational works of Jerry Weinberg, participating in community-driven initiatives like Weekend Testing, and actively engaging with testing blogs.
Tools vs. Critical Thinking
Addressing the age-old debate over whether analytical and critical thinking trump tool and process expertise, Bolton uses an apt 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."
While automation tools and process frameworks are vital force multipliers, they remain fundamentally unreliable and shallow in the absence of human analysis and critical thinking. Tools aid the mind; they cannot replace it.
Official Responses and Perspectives: Inside Rapid Software Testing
A major highlight of the interview is Bolton’s discussion of Rapid Software Testing (RST), a program widely regarded as one of the premier training methodologies in the field.
Unlike traditional courses designed around memorizing terminology to pass automated exams, RST features no exams at all. While vocabulary is valued for sharpening concepts, RST focuses heavily on deep reflection, practical application, and peer collaboration.
"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," Bolton explains.
In RST and RST Applied classes, participants do not sit through passive lectures; they actively test live software, solve complex puzzles, and rigorously debate their findings. Bolton notes that this interactive philosophy is shared by other elite programs, such as Rob Sabourin’s Just in Time Testing classes and the intensive BBST curriculum. These programs succeed because testing is an empirical craft that demands rigorous, hands-on practice.
Implications: The Future Landscape for Testers
As software engineering evolves, what does the future hold for professionals in the QA space? Bolton outlines both alarming risks and hopeful transformations.
The Dangers of Bureaucracy and Confirmatory Testing
Organizations that cling to the belief that testing is merely about following someone else’s scripted instructions are headed for a reckoning. As AI and machine learning continue to advance, rote, script-based checking will be almost entirely delegated to machines.
Testers who fail to evolve beyond manual script execution face a stark choice: upskill their programming, analytical, and social-science capabilities, or risk displacement. Conversely, testers who act as genuine experimenters, analysts, and designers will find themselves indispensable.
The Rise of Testing as a Universal Skill
Looking toward broader industry trends, Bolton expresses hope that software testing will eventually be recognized not as a siloed department, but as a core set of skills that pervades the entire software development lifecycle. In an ideal future, developers, product designers, and business stakeholders alike will integrate testing mindsets into their daily routines.
However, realizing this vision requires actively elevating the baseline skills of testers worldwide.
The Ultimate Skill: Telling the Testing Story
When asked for actionable advice on how upcoming testers can achieve success, Bolton points to a critical blind spot in the industry: the ability to tell the testing story.
According to Bolton, a compelling testing story is woven from three distinct, interdependent strands:
- The Product Story: Detailing the product’s current status—what it does, what it fails to do, how it operates, and how it might fail in ways that genuinely matter to stakeholders.
- The Methodology Story: Explaining how the testing was conducted, the setup environments, the heuristics and oracles applied, test coverage metrics, and the critical testing areas left unexplored due to constraints.
- The Craftsmanship Story: Describing the quality of the testing process itself, the obstacles that made testing harder or slower, the product’s inherent testability, and concrete recommendations to make future testing deeper, faster, and more effective.
Conclusion
Michael Bolton’s insights serve as both a warning and a roadmap for the software testing community. As automation and artificial intelligence reshape the technical landscape, the era of mindless script-following is drawing to a close.
The future belongs to the thinkers, the investigators, and the storytellers—those who view testing not as a box-checking exercise, but as an endless university of technical discovery. For aspiring and veteran testers alike, the mandate is clear: abandon the empty pursuit of paper certifications, sharpen your critical thinking, and learn to tell the story of your testing with clarity, depth, and conviction.
Special thanks to Mr. Michael Bolton for sharing his time, wisdom, and philosophy with SoftwareTestingHelp and its global readership.
