这篇论文用86k条实际数据告诉你：AI写的测试代码虽然多，但八成没用断言，光靠数量验收会翻车。建议读读他们总结的oracle信号分类。
该论文分析了33,596个AI Agent（OpenAI Codex、GitHub Copilot、Devin、Cursor、Claude Code）提交的86,156个测试文件补丁，发现80.2%的测试补丁包含弱或没有显式断言（oracle signals）。研究者总结出8种oracle信号类型，并发现经过回归分析调整后，强oracle信号使PR合并可能性提高28%（OR=1.28, p<0.001）。结果表明仅凭测试文件数量会高估验证强度。
All Smoke, No Alarm: Oracle Signals in Agent-Authored Test Code
Software practitioners increasingly use AI coding agents that generate test code alongside production code in open source pull requests (PRs). Recent studies report more than 932,000 agent-authored PRs across more than 116,000 repositories, yet whether their test files contain meaningful verification logic remains underexplored. Test files lacking explicit assertions execute code without verifying behavior, so quality gates based on test-file presence overestimate verification strength. The goal of this paper is to help practitioners assess the verification strength of agent-authored patches by characterizing oracle signals and their link to merge outcomes and review effort. We conduct an empirical study of 86,156 test-file patches from 33,596 agent-authored PRs across 2,807 GitHub repositories produced by five coding agents: OpenAI Codex, GitHub Copilot, Devin, Cursor, and Claude Code. A qualitative analysis of 384 stratified patches informs a syntactic taxonomy of eight oracle signal categories. Applied at scale, 80.2% of test patches contain weak or no explicit oracle signals. While raw merge rates are lower for strong-oracle PRs, a regression analysis adjusting for agent, PR size, repository popularity, task type, and language shows strong oracles significantly improve merge likelihood (OR = 1.28, p < 0.001). Our findings suggest that test file counts substantially overestimate verification strength and that practitioners can adopt oracle-aware quality checks to more accurately evaluate agent-authored contributions.