AI-Powered Software Testing: How QA Teams Are Changing
Every QA team seems to be using AI now. But many teams are still figuring out what that means in practice.
According to the World Quality Report 2025-26 from Capgemini, Sogeti, and OpenText, 89 percent of organizations are piloting or deploying generative AI in quality engineering. Roughly 1 in 7 have actually scaled it past the pilot stage. That gap between trying AI and running on it is where most of the real story sits, and it's exactly where software testing and QA services built around this shift earn their keep.
What AI actually does inside a test suite
Self-healing tests top the list. A UI element moves or gets renamed, and instead of the test breaking, the system adjusts the locator automatically and keeps running. Anyone who's spent a Monday morning fixing dozens of broken tests after a routine UI update knows the problem this can solve.
Test case generation from natural language is the other major use case. Describe a user's flow in plain language, and the system drafts the test cases instead of someone writing them line by line. Intelligent test selection and prioritization rounds it out, running the tests most likely to catch a regression first instead of running the entire suite top to bottom every time.
Generating tests isn't the same as testing the right things
72 percent of QA professionals now use AI to generate tests or optimize test scripts. That's a genuinely high adoption number, and it is also where the story gets more complicated than the headline suggests.
Many teams are using that capability to increase test volume: more test cases from requirements and more scripts from user stories. Fewer teams are checking whether that expanded coverage actually maps back to what the software is supposed to do. A suite that quadruples in size without a traceability model, behind it is a maintenance bill nobody budgeted for, arriving a few months later disguised as flaky CI runs, not the productivity win it looked like on the dashboard.
The QA role itself is shifting, not just the tools
41 percent of organizations report that their QA teams are evolving into quality engineering teams, with a greater focus on orchestration across pipelines, environments, and data rather than simply running test cases. 38 percent now involve business analysts directly in test creation, widening who writes and owns tests beyond the automation engineers who used to own that work alone.
That's a bigger shift than a new tool in the stack. It changes who is accountable for quality and means that testing knowledge once concentrated within QA is spreading into product and business roles.
The adoption curve isn't as smooth as it looks
In 2023, 31 percent of organizations reported not using generative AI in quality engineering. That fell to 4 percent in 2024, reflecting a sharp increase in adoption. In 2025-26, that figure rose again to 11 percent, suggesting that some teams may have encountered challenges while moving from experimentation to broader adoption.
That small reversal is worth paying attention to. It's not evidence that AI in QA is failing. It's evidence that piloting something and operationalizing it are two different stages, and moving from one to the other without the groundwork is exactly how a team ends up back at zero.
What separates the teams that actually scale it
Two factors stand out in the data: the quality and connectivity of an organization's underlying data, and the regulatory or compliance requirements that can affect the move from pilot to production. Teams with fragmented test data across disconnected tools can struggle to move beyond the pilot stage, regardless of the AI tooling they use.
Experience matters more than team size. Automation engineers with five or more years of experience report higher rates of AI to use within their teams than newer team members. This may suggest that experience and knowledge play a role in determining which parts of the testing process teams are comfortable handing off to AI.
What this looks like in a working QA team
A test suite flags a failure after routine deployment. Self-healing catches half of it automatically, adjusting a renamed button before anyone notices. The remaining failures can be prioritized, while AI-assisted root cause analysis can help identify the likely commit before a team member investigates the logs.
The team that built that traceability model six months before the AI rollout is the one seeing real time savings now. The team that skipped straight to test generation is the one drowning in a suite twice the size with no clearer picture of what is actually covered. If you're trying to close that gap, The One Technologies can help build the QA foundation needed to support effective AI-driven testing.
