# Why this conversation matters right now > AI is already reshaping how software is built and tested. Four testing leaders ask who owns quality now, and what happens to the human tester. - Series: The Future of Software Testing (No. 01 · The series opener) - Author: Alex Martins, VP of AI Transformation ([LinkedIn](https://www.linkedin.com/in/alexmartinsit/)) - Published: 2026-09-30 - Reading time: 5 min read - Canonical URL: https://thefutureofsoftwaretesting.com/articles/why-this-conversation-matters-now/ AI is no longer on the horizon. It is already reshaping how software is built, tested, and released - faster than most quality processes were designed to absorb. Developers are shipping AI-written code at speed. Test teams are generating cases, maintaining suites, and triaging defects with AI. But speed cuts both ways. AI magnifies the process it enters. Strong quality practices can become faster and more scalable. Weak coverage, poor assumptions, fragmented ownership, and insufficient oversight can scale just as quickly. More AI-generated tests do not automatically mean more confidence in a release. So the question is no longer whether AI will change software quality. It already has. The more important question is whether our testing practices, team structures, skills, and accountability models can evolve fast enough to keep pace. And while a growing market of tools promises increasingly autonomous testing, technology alone cannot answer the harder questions of judgment, ownership, and accountability. That is the conversation at the heart of The Future of Software Testing - a series bringing together different perspectives on how AI is reshaping software quality and the people responsible for it. ## Voices in the conversation The series brings together perspectives from across software testing, product, AI, and quality engineering. These voices have watched AI change how software gets built - and are examining what that means for how software earns trust. - Vu Lam brings the founder’s perspective: a long view of how testing has evolved across agile, automation, and now AI-assisted delivery. - Cristiano Caetano brings the product architect’s perspective: how testing platforms should support real engineering workflows, not just isolated features. - Alex Martins brings the perspective of the quality engineering leader trying to use AI to accelerate testing: what it actually means to build AI into testing workflows and separate practical value from hype. - Mush Honda brings the quality engineering perspective: how teams turn tools into process, evidence, accountability, and better release decisions. Together, these perspectives examine a fundamental question: What does quality require when AI can do more of the work? ## A point of view on AI and testing > **AI accelerates testing. People lead quality.** Code can now be generated in moments. Tests can be created, executed, analyzed and maintained with increasing autonomy. But more code, more tests, and faster delivery do not automatically produce better software. > AI will automate more testing work, while raising the bar for what skilled quality professionals contribute. > > - Mush Honda > The most useful way to think about AI today is as a new teammate, not a tool. Like any teammate, it does excellent work when you onboard it with context and judgment - and poor work when you don’t. > > - Alex Martins The future tester will not compete with AI on speed. Their value will increasingly come from what AI cannot provide on its own: judgment, context, accountability, and confidence. ## Questions shaping the conversation ![Fig. 01 - AI magnifies the process it enters: strong practices scale, weak coverage scales too](https://thefutureofsoftwaretesting.com/_astro/g-amplify.zysjp92C.png) *Fig. 01 - AI magnifies the process it enters: strong practices scale, weak coverage scales too* ### Who owns quality in the age of AI? As AI contributes more code and testing work, accountability becomes more complex. Who [validates AI-generated output](https://katalon.com/resources-center/blog/ai-testing-best-practices)? Who accepts the risk? Who decides whether the evidence is sufficient? And who is ultimately accountable for what reaches customers? Quality may increasingly become everyone’s responsibility. But shared responsibility can easily become unclear responsibility. ![Fig. 02 - Shared responsibility, contested centre: the release decision nobody clearly owns](https://thefutureofsoftwaretesting.com/_astro/g-ownership.CT-n6-c9.png) *Fig. 02 - Shared responsibility, contested centre: the release decision nobody clearly owns* ### What happens to the human tester? AI will automate more testing activities, but testing has never been only about executing test cases. Strong testers understand systems, challenge assumptions, uncover unexpected risks, and interpret whether the available evidence actually supports a release decision. As AI takes on more execution, the better question is: Where does human judgment create the greatest value? ### How should testers evolve? The strongest signal from the market right now is not anxiety. It is ambition. A growing number of professionals are reframing their roles around AI-augmented testing. They want to evolve, and they want to know how. We will give them a practical path. ## What comes next This month, The Future of Software Testing will begin exploring the questions shaping the next era of software quality. The goal is not to arrive at one definitive answer, but to bring sharper perspectives into the conversation - and invite the testing community to challenge them. What feels incomplete? Where do you disagree? What is the industry still avoiding? > The future of software testing should not be dictated by AI vendors or defended by those protecting the past. It should be shaped by practitioners who know the craft - and are ready to evolve with what quality demands next. > > - Vu Lam The value of this series will not only come from what we publish. It will come from the conversation it opens. This is our invitation to examine that future together. --- ## About the author **Alex Martins**, VP of AI Transformation With over two decades across software development, enterprise technology, testing, and AI, Alex has worked closely with engineering and quality teams through major shifts in how software is built and tested. He is also a published author and a long-time voice on the evolution of software quality. In The Future of Software Testing, Alex brings a critical, pragmatic perspective - challenging conventional thinking, cutting through AI hype, and asking the uncomfortable questions about what is truly changing for testers and engineering teams.