80% of firms have traced a production incident to AI-written code. AI code testing is now a buying criterion

A Sauce Labs survey of 400 engineering leaders finds 83% run production code that is over 10% AI-generated, 80% have traced an incident to it, and 92% doubt their safeguards. Searches for AI code testing and verification are rising as a result.

Searches for “AI code testing” and “AI code verification” are climbing, and a July 2026 Sauce Labs survey of 400 US executives and engineering leaders explains why. 83% of organisations now run production code that is more than 10% AI-generated. 80% have directly traced a production incident back to it. 92% say they are not confident their safeguards would catch an AI-driven failure before users do.

The number that matters most

66% admit they have compromised on quality or testing standards just to hit a release date. And 64% have increased QA headcount even though AI is writing more of the code. Writing code got cheap and fast. Proving it works did not.

What this means for the way you buy

Every AI coding tool, from Claude Code to Cursor to Copilot, produces working-looking code at speed. Working-looking is not the same as correct. The failures that reach customers are the quiet ones: an edge case in payments, a permissions check that is missing, a screen that breaks on an older phone.

The same survey found 89% report positive ROI from AI testing tools, so the answer is not to avoid AI-assisted development. It is to insist that testing scales with it.

Questions worth asking any developer or agency

Vague answers to these tell you the speed is being paid for later, by your users.

So what

AI has moved the bottleneck from writing software to verifying it. If a quote is dramatically faster and cheaper than the rest and says little about testing, the saving is probably borrowed from your launch week. BuildApps builds with AI tooling and keeps human review and automated testing in every release. See how that works in AI-assisted development, or start a project.

← All research

More research.

GitHub Copilot adds Supabase, Webflow, Wix and five more connectors in public preview

GitHub Copilot now connects to eight more services, including Supabase, Webflow, Wix and Mixpanel, through verified MCP connectors in public preview. They join more than 25 existing ones.

Read ›

Gemini 4 Neon is generally available in GitHub Copilot, aimed at lower-cost agentic coding

Gemini 4 Neon is now generally available in GitHub Copilot for agentic coding. Google says its quality is close to Gemini 4 Carbon at a lower token cost per task.

Read ›

Claude Code 2.1.328 brings auto mode to Bedrock, Vertex and Foundry, and narrows /code-review to bugs

Claude Code 2.1.328 extends auto mode to Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud and Microsoft Foundry. /code-review now reports only bugs and CLAUDE.md violations.

Read ›

GitHub Copilot Evals: repeatable tests for AI agents, now in public preview

GitHub Copilot Evals lets teams write repeatable tests for AI coding skills, custom agents and MCP tools. It checks both the result and the path the agent took, and is in public preview.

Read ›

GitHub Copilot can now drive your browser: browser use enters public preview

GitHub Copilot browser use lets an AI coding agent control Chrome to debug web apps and run browser tests. It is in public preview across the CLI, the Copilot app, VS Code and JetBrains.

Read ›

Claude Code 2.1.327 refuses some symbolic links and lists broken setup in /status

Claude Code 2.1.327 tightens file and package permissions again and adds a /status list of broken agent, skill and hook settings. A short read for teams using AI coding tools on a live product.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work