EUVIMEDEUVIMED entdecken
Open Access · CC BY 4.0

PROGnosticator: Testing Source-to-Source Code Translators via Construct-Oriented Fuzzing

Yeaseen Arafat, Stefan Nagy

Proceedings of the ACM on Software Engineering · 30.06.2026 · 3 (FSE) · 876-898

DOI: 10.1145/3797135 ↗

Kurz gefasst

Fachartikel in der Zeitschrift Proceedings of the ACM on Software Engineering, online erschienen am 30.06.2026. Verfasst von Yeaseen Arafat und 1 weiteren Autor:innen. Die Arbeit nennt 78 Literaturangaben. Der Volltext ist frei zugänglich (Open Access, CC BY 4.0). Gefördert von: National Science Foundation, Defense Advanced Research Projects Agency.

AbstractBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

To ease software interoperability and migration, developers are increasingly embracing transpilers: automated tools for converting source code from one language to another. Unfortunately, differences in language constructs, syntax, and semantics leave transpilers facing many translation bugs, emitting incorrect or non-functional translations. Thorough, proactive transpiler testing is thus critical to the reliability of emergent translation-oriented development. While fuzzers excel in testing adjacent classes of language processors (e.g., compilers), current fuzzers remain tied to only the specific code patterns expressed in their inputs— hardcoded grammars or seed programs—which are costly to curate and extend, constraining their testing to just narrow subsets of language constructs. Worse yet, their generated programs are often overly complex, requiring non-trivial reduction to pinpoint the exact code patterns behind transpiler errors. Evaluating current and future transpilers thus demands a rigorous, input-independent fuzzing strategy—systematically exercising languages’ broad range of code constructs without needing costly per-language expertise or re-engineering. To bridge this gap, we present Construct-oriented Fuzzing: a language-agnostic yet construct-aware approach for systematically testing transpilers. Motivated by our insights from past transpiler bugs, revealing most translation errors embody construct-specific mishandling, our approach explicitly targets the vast space of code patterns derived from core language constructs. Harnessing large language models’ code understanding and synthesis, we (1) automatically enumerate a language’s core constructs, before (2) generating self-contained programs exercising them individually—and combinations thereof—precisely testing transpilers’ many edge-cases whilst eschewing cumbersome grammars or seeds. In evaluating our prototype, PROGnosticator, against four state-of-the-art compiler and transpiler fuzzers across seven transpilers for C, Go, and JavaScript, we show how our approach attains high per-language validity as well as construct-usage diversity—exposing 77 total transpiler bugs, of which 64 are previously unknown, with 63 since confirmed or fixed by developers.

Förderung

  • National Science Foundation
  • Defense Advanced Research Projects Agency

Zitieren

APA

Arafat, Y., & Nagy, S. (2026). PROGnosticator: Testing Source-to-Source Code Translators via Construct-Oriented Fuzzing. Proceedings of the ACM on Software Engineering, 3(FSE), 876-898. https://doi.org/10.1145/3797135

Vancouver

Arafat Y, Nagy S. PROGnosticator: Testing Source-to-Source Code Translators via Construct-Oriented Fuzzing. Proceedings of the ACM on Software Engineering. 2026;3(FSE):876-898. doi:10.1145/3797135

BibTeX
@article{Arafat2026,
  author = {Arafat, Yeaseen and Nagy, Stefan},
  title = {PROGnosticator: Testing Source-to-Source Code Translators via Construct-Oriented Fuzzing},
  journal = {Proceedings of the ACM on Software Engineering},
  year = {2026},
  volume = {3},
  number = {FSE},
  pages = {876--898},
  doi = {10.1145/3797135}
}
Kostenlos starten →