All Smoke, No Alarm: Oracle Signals in Agent-Authored Test Code
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
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.
Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 7 of its 20 references that are in the map. First posted on arXiv 16 Jun 2026.
Builds on
7 of 20 references.
Closest ancestors · 4
Same direction, newest first
- 2026From Industry Claims to Empirical Reality: An Empirical Study of Code Review Agents in Pull Requests3 Apr
- 2026AIDev: Studying AI Coding Agents on GitHub9 Feb
- 2026Human-Agent versus Human Pull Requests: A Testing-Focused Characterization and Comparison29 Jan
- 2025On the Use of Agentic Coding: An Empirical Study of Pull Requests on GitHub18 Sep
Other references · 3
Built on by
Citing papers per year: 2026: 1.
1 paper.
Similar, not cited
Close in wording, no citation either way
- 2026Beyond Test Presence: Assessing the Quality and Robustness of Agent-Generated Tests in Open-Source Projects
- 2026Where Do AI Coding Agents Fail? An Empirical Study of Failed Agentic Pull Requests in GitHub
- 2026Do Autonomous Agents Contribute Test Code? A Study of Tests in Agentic Pull Requests
- 2026Not All Agents Are Equal: Code Quality and Post-Merge Maintenance Across Five Autonomous Coding Agents in the Wild
- 2026Test Coverage Analysis of Agentic Pull Requests
- 2026Why Are AI Agent Involved Pull Requests (Fix-Related) Remain Unmerged? An Empirical Study
- 2026Beyond Bug Fixes: An Empirical Investigation of Post-Merge Code Quality Issues in Agent-Generated Pull Requests
- 2026How AI Coding Agents Modify Code: A Large-Scale Study of GitHub Pull Requests