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

By the SoftwareTestingHelp (STH) Editorial Team

1. Main Facts

In an industry rapidly being reshaped by automation, artificial intelligence, and shifting development paradigms, the fundamental philosophy of software testing often gets lost in translation. To help clear the noise, SoftwareTestingHelp (STH) recently sat down with renowned software testing teacher, author, consultant, and thought leader Michael Bolton.

As part of STH’s ongoing “Know The Leader” interview series—which previously featured industry heavyweights like Neeraj Tripathi, VP of Global QA at Infor—Bolton offered a masterclass in modern quality assurance.

The conversation spanned decades of technological evolution, stripping away corporate buzzwords to focus on the core tenets of software testing: critical thinking, deep analytical capability, and the art of storytelling. Bolton, widely known for co-creating the pioneering Rapid Software Testing (RST) methodology alongside James Bach, pulled no punches regarding the state of modern QA. He addressed the low standards often plaguing the industry, the fallacy of standard test certifications, and the looming threat that rote script-following poses to manual testers in an automated world.

For software engineering professionals, QA leads, and aspiring testers alike, Bolton’s insights serve as both a cautionary tale and a roadmap for career survival and growth.

2. Chronology: The Evolution of a Tester

Understanding how Michael Bolton arrived at the pinnacle of software testing thought leadership requires looking back at a diverse, multidisciplinary journey. When asked about his entry into the field, Bolton explained that the timeline isn’t linear.

• Early Beginnings (School Years & 1988): Bolton’s journey unofficially began during his school days editing the student newspaper—an early exercise in spotting errors, structuring narratives, and editing content. By 1988, he was actively writing software.
• The Technical Support Era (1990): Transitioning into technical support in 1990 provided Bolton with frontline exposure to user pain points, system failures, and real-world software friction.
• The Quarterdeck Milestone (circa 1994): Combining his skills in writing code, providing support, and evaluating systems, Bolton was officially offered a role with the formal job title of "Software Tester" at Quarterdeck in 1994.
• Present Day: Decades later, Bolton operates as a globally recognized consultant, corporate trainer, and author, running the acclaimed DevelopSense blog and shaping the minds of thousands of testers through immersive training programs.

3. Supporting Data and Industry Context

Bolton’s perspectives on testing are backed by structural challenges that continue to plague the global IT ecosystem:

• The Training Gap: Traditional corporate environments often rely on rote checklist testing and heavy documentation, which Bolton distinguishes from true testing. According to industry observations, organizations that treat testing as a clerical check-box exercise suffer from higher rates of escaped production defects.
• The Certification Debate: Despite the billion-dollar market for foundational testing certifications (such as ISTQB), industry veterans frequently note a disconnect between multiple-choice exam success and practical, exploratory bug-hunting capability. Bolton’s philosophy aligns with a growing movement favoring competency-based learning (like BBST and RST) over paper credentials.
• The Threat of Automation vs. Checking: As automated pipelines and script-running tools become commoditized, routine test execution is increasingly absorbed by machines. Testers who rely solely on script execution face career displacement, while analytical testers who treat software as an empirical science remain indispensable.

4. Official Responses and Insights: The STH Q&A with Michael Bolton

Below are the highlights from the exclusive STH interview, capturing Bolton’s unfiltered thoughts on the craft of software testing.

On the Joy of Testing

When asked about the best part of his profession, Bolton pointed to the perpetual learning curve:

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

Demystifying Rapid Software Testing (RST)

Addressing whether RST is a one-of-a-kind framework, Bolton clarified that while RST avoids memorization-heavy exams, it emphasizes deep conceptual framing.

"Lots of classes focus on memorizing terminology so that you can pass an exam. We don’t have exams… 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."

He noted that while RST is popular for its hands-on puzzles and interactive exercises, similar rigorous methodologies exist in Rob Sabourin’s Just in Time Testing classes and the longer-form Black Box Software Testing (BBST) courses. Practice, not passive listening, remains the common denominator.

The Core Challenges: Low Standards and Misunderstandings

Bolton didn’t shy away from diagnosing why testing is frequently viewed as an under-appreciated discipline.

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

This creates a vicious cycle where management expects little value from QA, invests minimally in upskilling, and consequently receives low-value execution.

Analytical Thinking vs. Tool Expertise

When presented with the classic dichotomy—analytical thinking versus tool expertise—Bolton rejected the premise:

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

The Certification Fallacy

Bolton offered direct advice to professionals wondering if certifications guarantee career advancement:

"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." He also strongly recommended reading the works of Jerry Weinberg and participating in community initiatives like Weekend Testing.

5. Implications for the Future of Software Testing

Bolton’s interview paints a vivid picture of where the software testing industry is heading—and who will survive the transition.

The Dangers of Script-Centric Bureaucracy

Organizations that view testing as a bureaucratic checklist exercise are headed for a reckoning. Bolton warns that when testing is reduced to operating a product with specific inputs to look for pre-determined outputs, it ceases to be testing; it becomes "checking."

Because checking can be easily automated, scripted testers face bleak career prospects unless they upgrade their capabilities. Testers who master programming, advanced data analysis, social sciences, or deep product experimentation will thrive, while passive script-followers will find themselves obsolete.

The Shift Toward Ubiquitous Testing Skills

Looking toward future trends, Bolton expressed a visionary hope:

"My hope is that testing will be recognized as a key set of skills that pervades all of software development, and that more developers, designers, and business people will take on those skills."

Rather than isolating QA as a siloed department at the end of a pipeline, modern engineering cultures are moving toward shared accountability for quality. However, Bolton stresses that specialized testers will always be needed to collaborate with cross-functional teams—provided the global baseline of testing skills is actively upgraded.

The Art of Telling the Testing Story

When asked for actionable advice on how upcoming testers can achieve success, Bolton highlighted a frequently neglected superpower: the skill of telling the testing story.

According to Bolton, a robust testing narrative relies on three interwoven strands:

1. The Product Status: What the software does, what it fails to do, how it operates, and how it might fail in ways that impact real-world clients.
2. The Methodology: How the testing was executed—setup procedures, operational vectors, coverage metrics, and the oracles used to recognize anomalies.
3. The Quality of the Testing: An evaluation of constraints, testability features, and actionable recommendations to make future testing deeper, faster, and more effective.

Conclusion

Michael Bolton’s interview with SoftwareTestingHelp is a vital reminder that testing is fundamentally a cognitive science, not a clerical task. For practitioners willing to embrace critical thinking, reject hollow credentials, and master the art of communicating risk, the future of software testing is brighter—and more intellectually stimulating—than ever.

For more exclusive insights, industry interviews, and QA tutorials, stay tuned to SoftwareTestingHelp (STH).