Elevating the Craft of Software Testing: An In-Depth Interview with Thought Leader Michael Bolton

By the SoftwareTestingHelp (STH) Editorial Team

Main Facts: The State of Modern Software Testing

In the rapidly evolving landscape of software engineering, the discipline of quality assurance (QA) and software testing often sits at a precarious crossroads. While technological complexity increases by the day, the fundamental perception and execution of testing within organizations frequently remain stagnant. To shed light on the realities of the craft, SoftwareTestingHelp (STH) sat down with globally renowned software testing teacher, author, consultant, and industry thought leader Michael Bolton.

As part of STH’s exclusive "Know The Leader" interview series—following previous high-profile conversations with industry leaders like Neeraj Tripathi, VP of Global QA at Infor—Bolton offered a masterclass on the philosophy, challenges, and future of software testing.

Key takeaways from Bolton’s insights include:

• The Definition of Testing: Testing is a lifelong learning journey that spans technical support, development, and hands-on exploration.
• The Value of Training: Programs like Rapid Software Testing (RST) emphasize critical thinking, interactive problem-solving, and deep craft exploration over rote memorization or exam-passing.
• The Industry’s Biggest Threat: Misunderstandings from management regarding the true nature of testing often lead to low standards, unskilful hiring, and an over-reliance on rigid scripts.
• The Core Competency: Testers must master the "art of telling the testing story," encompassing product status, testing methodology, and the quality/constraints of the testing process itself.

Chronology: From Early Tech Roots to Global Thought Leadership

Michael Bolton’s journey into the world of software testing was not linear; rather, it was forged through decades of diverse multidisciplinary experiences. Tracing his timeline reveals how foundational experiences across publishing, software development, and technical support converged to build a premier testing career.

• Pre-1988 (The Formative Years): Bolton’s early exposure to communication and information management began with editing his school newspaper—an experience that cultivated a lifelong appreciation for clarity, investigation, and narrative structure.
• 1988 (Entering Software Development): Bolton began actively writing software, gaining a builder’s perspective on how code is constructed, how logic breaks, and how systems are architected.
• 1990 (The Technical Support Era): Transitioning into technical support, Bolton engaged directly with end-users experiencing software failures. This period was crucial in understanding how real people interact with systems and where expectations diverge from technical reality.
• 1994 (Joining Quarterdeck): Synthesizing his backgrounds in writing, development, and support, Bolton was officially offered a role bearing the title of "software tester" at Quarterdeck.
• Present Day: As a prominent consultant, co-creator of Rapid Software Testing (RST), and vocal advocate for contextual testing, Bolton spends his time teaching, writing, and reshaping how global enterprises view quality and investigation.

Supporting Data & Expert Perspectives: Deconstructing the Testing Landscape

During the interview, Bolton challenged several long-standing dogmas within the software quality assurance industry. His perspective is backed by decades of consulting experience observing what separates high-performing testing teams from struggling ones.

1. Training vs. Certification

When asked about the value of industry certifications, Bolton was unequivocal. Most mainstream certifications, he noted, measure an individual’s ability to memorize terminology rather than their practical capability to discover bugs, model systems, or evaluate risk.

• The Alternative: Bolton recommends active self-education. He points aspiring professionals toward the Basic Black Box Software Testing (BBST) course material, the Rapid Software Testing (RST) curriculum, the foundational literature of Jerry Weinberg, peer-led communities like Weekend Testing, and active engagement with testing blogs.

2. Tools and Process vs. Critical Thinking

Addressing the perennial debate over whether tools and processes outweigh analytical capabilities, Bolton offered a vivid 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 agile processes can aid a tester, they are entirely useless—and potentially dangerous—in the absence of human analysis, critical thinking, and systems evaluation.

Official Responses: Michael Bolton in His Own Words

The core of the STH interview dives deep into Bolton’s philosophy on the past, present, and future of software testing. Below are edited highlights from the conversation regarding specific industry challenges and career advice.

On the Best Part of Being a Software Tester

"Testers not only get to learn about technology, business domains, and problems, but they get paid to do it. Testing is a university, where the program lasts your whole career."

On Rapid Software Testing (RST) and Interactive Learning

"Lots of classes focus on memorizing terminology so that you can pass an exam. We don’t have exams… People who like Rapid Software Testing and Rapid Software Testing Applied classes enjoy the fact that, in class, we test software, work on puzzles, and then we talk about what happened and what we’ve learned. Testing requires practice, not just talking."

On the Biggest Challenges Facing Testing Teams

"The biggest challenge that I see is that employers misunderstand testing, and therefore hold it to a low standard. It’s too easy for some testers to remain unskilled because even the managers who hire them are unskilled. At the same time, many testers don’t work on their skills… so the situation amplifies itself."

On Destructive Industry Trends and "Checking" vs. "Testing"

Bolton issued a stark warning regarding the mechanical execution of scripted test cases:

"Some people seem to believe that testing is all about bureaucracy and paperwork; about rote execution of test procedures following a script… When that kind of work can be done by algorithms, by computer programs, we call that ‘checking’… Sooner or later, people are going to realize that testing centered around confirmatory test cases is not very informative and not very valuable."

He cautioned that testers who rely solely on following instructions must choose to upgrade their programming, analytical, or social-science skills, or risk obsolescence. Conversely, experts in analysis, design, and experimentation will thrive.

On the Ultimate Skill: Telling the Testing Story

When asked what advice he has for upcoming testers, Bolton emphasized the art and structure of communication:

"There’s one key skill in which I observe most testers seem unfortunately weak, and that’s the skill of telling the testing story."

According to Bolton, a comprehensive testing story is woven from three distinct strands:

1. The Product Status: What the product does, what it fails to do, how it works, and how it might fail in ways that matter to stakeholders.
2. The Testing Methodology and Coverage: How the product was set up, operated, and investigated; what oracles were applied; and crucially, what has not yet been tested.
3. The Quality of the Testing Process: Why the testing performed was the best possible under given constraints, what made testing harder or slower (such as poor product testability), and what resources are required to make future testing faster and deeper.

Implications: The Future of Quality Assurance

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

For Organizations and Management

Companies must move away from viewing testing as a bureaucratic checklist or a low-cost, late-stage verification gate. If corporate leadership continues to misunderstand testing as mere script-following, they will attract unskilful talent, build brittle automation suites, and miss critical systemic risks. Organizations must foster environments where exploratory testing, critical thinking, and deep technical curiosity are prioritized and rewarded.

For Software Testers

The era of the "script-follower" is drawing to a close. With advancements in artificial intelligence and automated checking, the market has less and less room for manual execution without cognitive depth. To remain indispensable, practitioners must embrace continuous education, hone their analytical frameworks, and master the ability to articulate software risk through clear, compelling narratives.

As Bolton notes, testing is not about finding a single "magic" skill, but rather about cultivating a mindset of relentless inquiry—continually asking when looking at any system, "What else could this be?"

For more exclusive interviews, industry insights, and career resources, stay tuned to SoftwareTestingHelp (STH). Feel free to leave your feedback, suggestions, or requests for future interviewees in the comments section below.