Test data wait times are slowing AI adoption more than code ever did
The New Stack Woody Evans
AI can write and test code in minutes, but getting real test data still takes weeks for most companies. That gap is now the actual bottleneck, not the coding itself.
Based on reporting by The New Stack, Woody Evans — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
For two years the industry obsessed over how fast AI could write code. Turns out that was the easy part. A new report from Perforce Delphix on test data management found that 99% of organizations wait more than a business day to get production test data, and 42% wait weeks or even months. Meanwhile, agentic tools are spitting out working features in hours. That mismatch is not a minor inconvenience — it is where the whole delivery pipeline grinds to a halt.
The report pins the problem on three things: fragmented, manual workflows with no single owner; quality checks bolted on as gates instead of built into the pipeline; and governance rules, especially in healthcare and financial services, that slow things down because compliance was never automated in the first place. None of these are exotic problems. They are the same paperwork-and-approval friction that agile and CI/CD were supposed to have already solved for code, except nobody applied the same discipline to test data.
And that is really the point here — this is a workflow design failure, not a missing tool. Ninety-eight percent of enterprises still rely on manual steps somewhere in their test data provisioning process. Code gets versioned, environments get spun up on demand, but data requests still get routed through tickets and human reviewers like it's 2012. Teams generate AI code faster than they can validate it, which just means unvalidated changes pile up instead of shipping.
The fixes described aren't complicated in concept: automate the entire provisioning lifecycle rather than one step of it, make compliant data the default output instead of a prerequisite, treat test environments as disposable rather than something maintained for months, and wire data delivery into CI/CD through APIs so it actually keeps pace with code generation. Worldpay cut environment setup from 28 days to four. Molina Healthcare went from days to under 10 minutes for provisioning and shaved three months off project timelines. Delta Dental moved test data to the cloud in hours instead of eight weeks. These aren't lucky outliers — they're what happens when someone finally treats test data with the same urgency as the code sitting next to it.
The framing shift the report pushes is simple but overdue: the competitive question in AI-driven development isn't who writes code fastest, it's who can validate it fastest. Companies that don't fix this will just get really good at generating code nobody trusts enough to ship.
My take — AI-written commentary, not fact-checked reporting
This tracks with something I've been saying for a while: every time we accelerate one part of the software pipeline, the bottleneck just migrates to whatever we didn't bother automating, and test data is the classic case of an invisible dependency nobody budgeted for. It's a vendor report, sure, so take the specific stats with a grain of salt, but the underlying pattern — AI making creation cheap while validation stays stuck in ticket queues — is exactly the kind of unglamorous infrastructure problem that determines who actually ships AI-generated code versus who just demos it.
Read more about this at: The New Stack
Related stories
The agent evaluation gap: Enterprise AI organizations have a reality-alignment problem, not a coverage problem — and most are shipping to production anyway
VentureBeat · 2 months ago ·
20
Turning 10x developers into 10x value
The New Stack · 1 month ago ·
11