Inside the Mind of a Testing Icon: An In-Depth Interview with Software Quality Thought Leader Michael Bolton

By the Software Testing Help (STH) Editorial Team

Main Facts: The State of Modern Software Testing

In an industry heavily driven by automated scripts, rapid delivery cycles, and an obsession with rigid certifications, the core essence of software testing is frequently misunderstood. To unpack the realities of the craft, Software Testing Help (STH) sat down with renowned software testing teacher, author, consultant, and thought leader Michael Bolton.

As part of the ongoing "Know The Leader" interview series—following previous high-profile features such as the discussion with Neeraj Tripathi, VP of Global QA at Infor—Bolton offered an uncompromising, deeply philosophical look at the state of quality assurance (QA).

Key takeaways from the exclusive interview include:

• The Definition of Testing: Bolton views testing not merely as execution, but as an ongoing university education where professionals are paid to explore technology, business domains, and complex problems.
• The Flaw of Certifications: Most testing certifications fail to measure actual testing capability; professionals are urged to prioritize deep self-education, mentorship, and practical application over exam prep.
• The Danger of "Checking" vs. "Testing": Rote execution of scripted procedures can increasingly be automated or handled by algorithms, threatening career security for passive testers who fail to adapt.
• The Power of Storytelling: One of the most neglected skills in testing is the ability to articulate a comprehensive "testing story" covering product status, testing thoroughness, and context-driven obstacles.

Chronology: A Journey from the Newsroom to the Forefront of QA

To understand Michael Bolton’s philosophy on software testing, one must examine the diverse pathway that shaped his career. Long before he became a globally recognized authority and co-creator of Rapid Software Testing (RST), Bolton’s professional DNA was forged through a rich mix of journalism, writing, technical support, and software development.

Early Beginnings and Foundational Skills

Bolton’s introduction to testing-like mindsets began long before he held a formal QA title. When asked about his entry into the field, he notes that there are multiple valid starting points:

• Editorial Roots: He jokingly points to his time editing his school newspaper as an early form of quality control and information curation, though he acknowledges it belongs to a distant era.
• Direct Interaction: Using early consumer and enterprise software provided a foundational understanding of user friction points and expectations.
• Coding and Support: Around 1988, Bolton began writing software, followed by a transition into technical support in 1990.

Entering the Formal Industry

The convergence of these distinct experiences—writing, coding, diagnosing customer pain points, and analytical problem-solving—ultimately qualified him for a formal position in the software domain. Around 1994, Bolton was officially offered a job with the title "software tester" at Quarterdeck, a major software company of the era known for its memory-management utilities.

Over the subsequent decades, Bolton transitioned from a corporate practitioner to an independent consultant, educator, and thought leader, eventually co-developing the internationally acclaimed Rapid Software Testing methodology with James Bach.

Supporting Data & Industry Insights: The Philosophy of Rapid Software Testing

Bolton’s influence on the QA community is largely anchored in his critique of conventional, bureaucratic testing paradigms and his advocacy for context-driven practices.

The Fallacy of Rote Testing and "Checking"

A central pillar of Bolton’s teaching is the critical distinction between testing and checking.

• Checking involves operating a product with specific inputs, following predefined scripts, and looking for predetermined outputs. Because this process is algorithmic and procedural, it can increasingly be delegated to machines and automated scripts.
• Testing, conversely, is an open-ended, intellectual investigation. It requires human critical thinking, real-time experiment design, and contextual evaluation.

Organizations that treat testing as a mere paperwork exercise or a rote administrative chore hold the discipline to a dangerously low standard. According to Bolton, this creates a vicious cycle: unskilled managers hire unskilled testers, leading to superficial quality assurance that ultimately offers little real value to stakeholders.

The Role of Training: Beyond Memorization

Discussing the success of the Rapid Software Testing (RST) and Rapid Software Testing Applied classes, Bolton emphasizes that true mastery cannot be achieved through passive study or exam memorization.

Unlike traditional certification bodies that test vocabulary via multiple-choice questions, RST relies on interactive exercises, live software exploration, and collaborative puzzle-solving. Bolton compares the efficacy of RST to other practical frameworks, such as Rob Sabourin’s Just in Time Testing classes and the Black Box Software Testing (BBST) courses. These programs succeed because they recognize a fundamental truth: testing requires hands-on practice, not just theoretical discourse.

Official Responses: Michael Bolton in His Own Words

During the STH interview, Bolton addressed several burning questions submitted by the software testing community. Below is a curated summary of his insights on key industry dilemmas.

On the Value of Certifications vs. Self-Education

"Most testing certifications don’t measure your ability to test. Don’t worry about getting certified. Concentrate on educating yourself. Look up BBST class material, or better yet, take a BBST class. Take the RST class if you prefer."

Instead of chasing acronyms on a resume, Bolton advises testers to read seminal works—such as the books of Gerald M. ("Jerry") Weinberg—participate in community-driven initiatives like Weekend Testing, and actively engage with peers on testing blogs.

On Analytical Thinking vs. Tool Expertise

When asked whether critical thinking or tool expertise is more vital for success, Bolton dismissed the dichotomy using 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."

Tools and automation frameworks are profoundly limited without human analysis and critical thinking to guide them. Conversely, brilliant analytical minds are significantly empowered when supported by deep technical tooling and process expertise.

On the Ultimate Advice for Aspiring Testers: Telling the Testing Story

When asked how new entrants into the field can achieve long-term success, Bolton pointed to a widespread weakness across the profession: the inability to tell a compelling testing story.

According to Bolton, a robust testing narrative is composed of three interconnected strands:

1. The Product Status: What the software does, what it fails to do, how it operates, and—crucially—how it might fail in ways that negatively impact real users and business stakeholders.
2. The Testing Methodology: How the product was configured and operated, where and how the tester searched for flaws, what coverage was achieved, and what important areas remain unexplored.
3. The Quality of the Testing Process: An honest evaluation of why the testing performed was the best possible under the given constraints, what environmental or architectural factors made testing harder or slower (such as poor testability features), and concrete recommendations to accelerate and deepen future QA cycles.

Implications: The Future Landscape of Software Quality Assurance

The views shared by Michael Bolton carry profound implications for software engineering organizations, QA leadership, and individual testing practitioners as the industry navigates the era of artificial intelligence and continuous integration.

The Evolution of the Tester’s Role

As artificial intelligence and advanced automation absorb routine "checking" tasks, the traditional manual script-follower faces an existential career threat. Testers who rely solely on executing pre-written instructions must evolve by upgrading their programming capabilities, sharpening their analytical and critical-thinking skills, or developing social-science proficiencies.

Conversely, testers who master the art of investigation, systems thinking, experiment design, and clear communication will find themselves increasingly indispensable to cross-functional product teams.

A Shift Toward Integrated Quality

Looking toward future trends, Bolton expresses optimism that testing will eventually be recognized not as an isolated, downstream 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 will naturally incorporate testing mindsets into their daily routines.

However, achieving this vision requires a foundational raising of skill levels across the global QA community. Organizations must move away from treating testing as an under-appreciated administrative hurdle and instead elevate it to a vital, intellectual pillar of engineering excellence.

For more exclusive interviews with software testing pioneers, stay tuned to Software Testing Help. Readers are encouraged to leave their thoughts, feedback, or suggestions for future interview subjects in the comments section below.