Skip to content

IssueExec: A Test-Driven Approach for Localizing Software Engineering Issues

Jul 2026 · arXiv.org · Vol abs/2607.17286 · 0 citations · 67 references
Computer Science

TL;DR

The proposed IssueExec bridges the semantic gap through domain-knowledge-enhanced test representations and filters noise via hierarchical trace analysis, which bridges the semantic gap through domain-knowledge-enhanced test representations and filters noise via hierarchical trace analysis.

Abstract

Issue localization, which identifies code locations requiring modification from issue descriptions, is a critical step in automated software maintenance. Existing approaches predominantly attempt to directly align issue descriptions with code elements, yet often struggle due to the inherent abstraction gap between the issue description and code implementation. Seeking alternative signals, our theoretical analysis suggests that test suites can serve as executable proxies for requirements, reducing localization uncertainty by 7.73 bits of entropy on average. A large-scale empirical study on 18 repositories validates this premise: existing tests cover 96.98\% of ground-truth files, and the two-hop pathway yields stronger semantic connectivity than direct matching in 82.4\% of cases. Despite their potential, leveraging tests for localization faces two key challenges: the semantic gap separating issue descriptions from test identifiers, and the substantial noise in execution traces from infrastructure code. To address these, we propose IssueExec, which bridges the semantic gap through domain-knowledge-enhanced test representations and filters noise via hierarchical trace analysis. Experiments on SWE-bench Lite show that IssueExec achieves state-of-the-art performance, improving function-level Recall@1 by 41.57\% over the strongest baseline. When integrated into the Agentless pipeline, IssueExec resolves 17.72\% more issues, demonstrating practical downstream benefits.

View source

Similar papers

Open access 2026

From Trace to Line: An Empirical Study of What Drives LLM-Based OSS Vulnerability Localization

This paper introduces T2L (Trace-to-Line), a reproducible research framework that narrows repository-scale code into candidate vulnerable lines through AST-based chunking, structured diagnostic information collection, and evidence-guided refinement that improves trace-to-line localization.

Haoran Xi, Minghao Shao, Brendan Dolan-Gavitt et al. · 0 citations
Jul 2026

DepRepair: LLM-Based Source-Code Repair for Dependency Breaking Changes

DepRepair is proposed, a single-call LLM approach that grounds repair in structured upstream evidence through three components: an evidence filter that distills relevant upstream changes, a usage locator that identifies affected consumer sites, and a subcategory-aware guide that tailors repairs to the breaking-change type.

Shenghao Yang, Bo Lu, Yao Liu et al. · 0 citations
Preprint Aug 2026

RepoProbe: Benchmarking Architecture-Aware Repository Comprehension with Checklists

This work introduces RepoProbe, a novel benchmark for evaluating repository-level code understanding through open-ended Q&A using GitHub Discussions, which focuses on open-ended architectural inquiries rather than defect reporting and proposes a Checklist-Based Verification Protocol that decomposes answers into atomic, verifiable facts, thereby replacing subjective ratings with objective verification.

Yue Yang, Alyssa Wu, Ji Luo et al. · 0 citations
Book Open access Jul 2026

RepoFuse: A Dual-Context Approach to Repository-Level Code Completion at Industrial Scale

RepoFuse, a dual-context framework deployed at Ant Group serving 10,000+ developers across 50+ million lines of code, is presented, demonstrating that principled context categorization enables practical repository-level completion at industrial scale.

Ming Liang, Xiaoheng Xie, Gehao Zhang et al. · 0 citations
Jul 2026

The Patchwork Problem in LLM-Generated Code

This paper formalizes structural coherence as consistency invariants over graph representations of repository artifacts, including import, call, dependency, configuration, schema, resource, control-flow, and routing graphs, and introduces an eight-category failure taxonomy distinguishing defects specific to LLM generation from those merely amplified by it.

Viraaji Mothukuri, R. Parizi · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.