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

By the SoftwareTestingHelp (STH) Editorial Team

Main Facts

The landscape of software testing is undergoing a rapid, often turbulent evolution. Driven by the relentless march of automation, artificial intelligence, and shifting development methodologies, the modern quality assurance (QA) professional faces a world vastly different from the one that existed a decade ago. Amidst this technological noise, few voices remain as consistently clear, challenging, and profoundly influential as that of Michael Bolton.

As part of the ongoing "Know The Leader" interview series on SoftwareTestingHelp—following previous high-profile features such as the discussion with Neeraj Tripathi, VP of Global QA at Infor—STH sat down with Bolton. A globally recognized software testing teacher, author, consultant, and thought leader, Bolton operates with a philosophy that cuts straight to the core of what it means to evaluate software in the modern age.

This in-depth feature explores Bolton’s journey into the craft, his views on the distinction between "checking" and "testing," the shortcomings of traditional certifications, and why he believes the ultimate superpower of any tester is the ability to tell a compelling testing story.

Chronology: From Newsrooms to Quarterdeck and Beyond

To truly understand Bolton’s perspective on software quality, one must look at the diverse trajectory of his career. Bolton’s entry into the tech sector was not linear; rather, it was built upon a foundation of varied experiences across media, code, and support systems.

• Early Beginnings: Bolton’s foundational exposure to the principles of communication and editing began in the school newspaper room. While he jokingly notes that this was "too long ago to mention," the editorial mindset—scrutinizing narratives, looking for gaps in logic, and demanding clarity—heavily influenced his later analytical approach to software.
• The Transition to Code (1988): Bolton began actively writing software, gaining a maker’s perspective on how digital systems are constructed, how code breaks, and how developers think.
• Technical Support Trench Work (1990): Moving into technical support forced Bolton to confront how real-world users actually interact with software—often in ways developers never anticipated. This frontline exposure to user frustration and system failure proved vital.
• Official Entry into QA (1994): All of these preceding experiences—editing, programming, and supporting users—culminated in an official job offer bearing the title "Software Tester" at Quarterdeck.

Since those early days, Bolton has transitioned from a corporate practitioner to an independent educator, consultant, and co-creator (alongside James Bach) of the world-famous Rapid Software Testing (RST) methodology. Through his blog, DevelopSense, and his rigorous training courses, he continues to shape how generations of testers view their professional identities.

Supporting Data & Industry Perspectives: Rethinking Training and Certifications

In the interview, Bolton challenged several long-held dogmas within the software testing industry, particularly regarding training programs, professional certifications, and the core skill sets required for longevity in the field.

Rapid Software Testing vs. Traditional Classrooms

Many industry training bodies focus heavily on rote memorization of terminology to help candidates pass standardized exams. Bolton distinguishes his approach—and those of other rigorous trainers like Rob Sabourin (Just in Time Testing) and the Black Box Software Testing (BBST) community—by focusing on active engagement rather than passive testing theory.

"We don’t have exams," Bolton explains. While vocabulary matters because it sharpens thought processes, RST does not mandate a specific corporate lexicon. Instead, students actively test software, solve complex puzzles, and debate outcomes. Because testing is fundamentally a physical and cognitive craft requiring practice, Bolton argues that interactive, workshop-style learning far outperforms theoretical, exam-based accreditation.

The Certification Myth

When asked for his advice on software testing certifications, Bolton did not mince words:

"Most testing certifications don’t measure your ability to test. Don’t worry about getting certified. Concentrate on educating yourself."

Instead of spending time and capital on paper credentials, Bolton encourages aspiring and practicing testers to dive into BBST course materials, read foundational literature (such as the works of Jerry Weinberg), follow industry blogs, and engage with collaborative practical communities like Weekend Testing.

Official Responses: Michael Bolton on the State of Modern Testing

Below are core excerpts from the STH interview, detailing Bolton’s official stance on some of the most pressing debates in quality assurance today.

On the Best Part of Being a 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 Analytical Thinking vs. Tool Expertise

When asked whether critical thinking or tool expertise is more important for a successful tester, Bolton used an illuminating 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 process expertise aren’t very reliable or useful in the absence of analysis and critical thinking."

On the Threat of "Checking" vs. Real Testing

Bolton issued a stark warning regarding the future of rote, script-following QA work, differentiating it sharply from true investigative testing:

"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’."

He cautioned that organizations relying entirely on confirmatory test cases executed by script-followers will eventually realize the low value of such work. Those unable or unwilling to pivot toward higher-level analysis, design, and experimentation risk displacement.

Implications: What the Future Holds for Software Quality Professionals

Bolton’s insights carry profound implications for the future of the software development lifecycle (SDLC). As artificial intelligence and automated testing frameworks absorb baseline functional verification ("checking"), the human tester’s role must evolve or face extinction.

1. The Death of Scripted Bureaucracy

Organizations that treat QA as a mechanical compliance task—where testers merely click through predefined scripts without applying critical thought—are on borrowed time. Code and machines can execute scripts faster, cheaper, and with fewer errors than humans. Testers who refuse to upgrade their analytical, programming, or social science skills will find themselves marginalized.

2. Testing as a Pervasive Skill Set

Looking forward, Bolton envisions a development culture where testing is not siloed away in a separate department, but is recognized as a fundamental skill set that pervades all of software engineering. Developers, designers, and business analysts who adopt testing mindsets will build more robust systems ab initio, while specialized testers will act as collaborative high-level consultants and experimenters.

3. The Power of the Testing Story

To secure their value within enterprise teams, testers must master what Bolton identifies as their most neglected competency: the skill of telling the testing story. According to Bolton, this story is a three-stranded braid:

1. The Product Status Strand: What the product does, what it fails to do, how it works under the hood, and crucially, how it might fail in ways that matter to clients.
2. The Methodology Strand: How the testing was designed and executed, what oracles were applied, and what coverage was achieved versus what remains unexamined.
3. The Quality of Testing Strand: An evaluation of the testing process itself—identifying what made testing harder or slower (such as poor product testability) and offering actionable recommendations to make future testing deeper, faster, and more effective.

Conclusion

Michael Bolton’s interview with SoftwareTestingHelp serves as both a reality check and an inspiring roadmap for QA professionals. In an era where technological displacement is a constant anxiety, Bolton reminds us that deep critical thinking, continuous self-education, and the ability to articulate risk and discovery cannot be automated away.

For aspiring testers and seasoned veterans alike, the message is clear: stop chasing meaningless certifications, step away from unthinking script execution, and start treating your career as an ongoing, inquisitive university.

You can follow Michael Bolton’s ongoing insights on his blog, DevelopSense, and connect with him on Twitter.

Stay tuned to SoftwareTestingHelp for more exclusive interviews with the most influential minds in global software testing. Have feedback, questions, or a specific industry leader you want us to interview next? Leave a comment below!