VOOZH about

URL: https://thenewstack.io/why-the-copilot-route-is-a-flawed-strategy-for-software-testing/

⇱ Why the Copilot Route Is a Flawed Strategy for Software Testing - The New Stack


TNS
SUBSCRIBE
Join our community of software engineering leaders and aspirational developers. Always stay in-the-know by getting the most important news and exclusive content delivered fresh to your inbox to learn more about at-scale software development.
REQUIRED
It seems that you've previously unsubscribed from our newsletter in the past. Click the button below to open the re-subscribe form in a new tab. When you're done, simply close that tab and continue with this form to complete your subscription.
The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy.
Welcome and thank you for joining The New Stack community!
Please answer a few simple questions to help us deliver the news and resources you are interested in.
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Great to meet you!
Tell us a bit about your job so we can cover the topics you find most relevant.
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Welcome!

We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.

What’s next?

Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.

Follow TNS on your favorite social media networks.

Become a TNS follower on LinkedIn.

Check out the latest featured and trending stories while you wait for your first TNS newsletter.

PREV
1 of 2
NEXT
VOXPOP
As a JavaScript developer, what non-React tools do you use most often?
Angular
0%
Astro
0%
Svelte
0%
Vue.js
0%
Other
0%
I only use React
0%
I don't use JavaScript
0%
Thanks for your opinion! Subscribe below to get the final results, published exclusively in our TNS Update newsletter:
NEW! Try Stackie AI
From clobbered drafts to real-time sync
Apr 14th 2026 10:00am, by David Moore
TypeScript 6.0 RC arrives as a bridge to a faster future
Mar 14th 2026 9:00am, by Darryl K. Taft
Mastra empowers web devs to build AI agents in TypeScript
Jan 28th 2026 11:00am, by Loraine Lawson
2025-03-31 10:00:26
Why the Copilot Route Is a Flawed Strategy for Software Testing
contributed,
AI / Low Code / No Code / Software Testing

Why the Copilot Route Is a Flawed Strategy for Software Testing

Software testing is evolving, but real efficiency requires more than just AI copilots.
Mar 31st, 2025 10:00am by Stephen Feloney
👁 Featued image for: Why the Copilot Route Is a Flawed Strategy for Software Testing
Photo by Christopher Gower on Unsplash.

I’ve spent over 25 years developing and bringing software testing products to market. During this time, we’ve witnessed significant changes — automated testing, continuous testing, low-code/no-code platforms, Centers of Excellence, and the shift-left approach. Yet, despite these advancements, one thing has remained constant: testing remains a time-consuming, inefficient bottleneck in the software development lifecycle.

Although testing has become less of a bottleneck over the years, we’ve never truly achieved seamless validation. Today, AI is at the forefront of the evolution of our testing products (as with many other vendors), but the key question remains: Will it make testing more efficient? What about the human element? Will AI reduce mundane tasks, or will it simply add another layer of complexity, as past “advancements” have done?

The Next Generation of Automated Testing

Many vendors have started incorporating AI into their testing platforms. Many have opted for AI copilots to assist in test creation, but this is only part of the solution. With AI advancing rapidly, we must look beyond copilots and focus on more meaningful accuracy, efficiency, and speed improvements.

While copilots can accelerate test creation, they don’t solve some of testing’s more significant challenges. Feedback from users has been mixed. Some developers find copilots helpful, but many report that they sometimes generate incorrect tests or create more tests that need ongoing maintenance. Instead of addressing core problems, copilots risk exacerbating them, simply layering AI over an already broken process.

Why Testing Is Still Broken

To understand why, let’s look at the evolution of automated software testing. The industry has developed various techniques for identifying objects on screen, enabling tests to run. While some methods work better than others, the fact remains that changes to the UI or application break tests necessitate constant maintenance — an estimated 30-40% of a tester’s time.

Take regression testing as an example: regression suites must be rerun whenever a change is made to detect new issues. In large applications, these tests can number in the thousands, yet it’s estimated that only 20% of tests in regression suites are valid. Many of these tests produce errors that require time-consuming analysis to verify their authenticity. It’s no wonder some enterprises still rely on manual testing, even though they know they can’t achieve full test coverage.

A New Approach To Testing

When discussing how to evolve web, mobile, and performance test suites, it was realized that while copilots assist in writing test scripts, they don’t address users’ most significant pain points: test maintenance and analysis. That’s why it’s best to focus on areas where value can be delivered, starting with test validation.

We need to rethink how to approach testing. Can the need for scripting and object-based locators be eliminated?

A Smarter Approach

The next evolution in automated testing is not simply visualizing what’s on the screen but using AI to understand it contextually and dynamically. By leveraging natural language processing, users can ask simple questions, and the system can analyze and validate tests accordingly without relying on objects or code or even needing to understand the underlying technologies of the applications. The result? Real-time validation that works across any platform and is usable by both technical and non-technical team members. It also survives massive changes to the code without manual intervention.

While the immediate benefits of AI-driven test validation are clear, the real value comes from hands-on experience and feedback from real users. Financial institutions, for example, have used this approach to validate data they could never validate before, such as checking whether on-screen graphs match the underlying tables. Retailers can now ensure product descriptions match product images. This AI-driven validation can work seamlessly, even as applications evolve, without requiring manual adjustments.

Moving Beyond Validation

But test validation is just the beginning. To truly transform testing, we must look at how AI can free testers and developers from routine tasks, allowing them to focus on more valuable work. The goal is to democratize testing — making it accessible and efficient for everyone. I am not a fan of the word “democratize”, but when used correctly, this is genuinely what AI will enable.

The future of software testing isn’t about applying AI for the sake of it or adopting short-term fixes. It’s about harnessing the most significant advancements in computing to solve real-world problems and finally fixing the broken processes plaguing software testing for years.

TRENDING STORIES
Stephen Feloney is VP of Products, Continuous Testing at Perforce. Prior to this role, he held product management roles at various companies from enterprise to startups including HP, CA, Broadcom, and others. Before product management, Stephen spent 12+ years a...
Read more from Stephen Feloney
SHARE THIS STORY
TRENDING STORIES
TNS owner Insight Partners is an investor in: Real.
SHARE THIS STORY
TRENDING STORIES
TNS DAILY NEWSLETTER Receive a free roundup of the most recent TNS articles in your inbox each day.
The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy.