SaaS & Software·Aug 3, 2026

AI migrated legacy COBOL programs to Java, bugs included

View PDF HTML (experimental) Abstract:Migration of legacy COBOL programs to Java requires extensive testing to ensure correct functionality. This effort is often complicated by the lack of test data and the difficulty of validating all corn

Hacker News1 min readSingle source
AI migrated legacy COBOL programs to Java, bugs included
Image · Hacker News
The gist
5-point summary · 1 min

View PDF HTML (experimental) Abstract:Migration of legacy COBOL programs to Java requires extensive testing to ensure correct functionality. This effort is often complicated by the lack of test data and the difficulty of validating all corn

  • View PDF HTML (experimental) Abstract:Migration of legacy COBOL programs to Java requires extensive testing to ensure correct functionality.
  • This effort is often complicated by the lack of test data and the difficulty of validating all corner cases.
  • When routing boundaries are reached, an analyzer identifies a Locked Paragraph: a condition preventing deeper exploration.
  • The generated Java matched the COBOL reference under deterministic parity checks in all accepted test cases.
  • Through these findings we demonstrate, to the best of our knowledge, a novel approach for validating agentic coding output using a deterministic oracle.
91.90%Jul 2026
In this article

View PDF HTML (experimental) Abstract:Migration of legacy COBOL programs to Java requires extensive testing to ensure correct functionality. This effort is often complicated by the lack of test data and the difficulty of validating all corner cases. In this paper we propose a novel agentic test-synthesis method, the "Locksmith Loop," which is initiated by preparing two runtime environments: the COBOL source and the generated Java target are each instrumented with mocks and executed off-mainframe on commodity hardware, then an iterative agentic loop performs Witness Search over input mocks to penetrate program branches, followed by parity-preserving mutations. When routing boundaries are reached, an analyzer identifies a Locked Paragraph: a condition preventing deeper exploration. Across three COBOL-Java case studies, spanning two open-source programs and one internal production-like COBOL program and ranging from 430 to 4,114 source lines, Locksmith consistently improved coverage beyond input-search plateaus, reaching nearly complete coverage on the two open-source programs and 91.90% branch coverage on the internal production-like COBOL program. The generated Java matched the COBOL reference under deterministic parity checks in all accepted test cases. Through these findings we demonstrate, to the best of our knowledge, a novel approach for validating agentic coding output using a deterministic oracle. Comments: 11 pages, 6 figures Subjects: Software Engineering (cs.SE); Artificial Intelligence (cs.AI) Cite as: arXiv:2607.28271 [cs.SE] (or arXiv:2607.28271v1 [cs.SE] for this version) https://doi.org/10.48550/arXiv.2607.28271 arXiv-issued DOI via DataCite (pending registration) Submission history From: Andras Ferenczi [view email] [v1] Thu, 30 Jul 2026 14:25:23 UTC (2,963 KB)

Integrity note  ·  Xela does not rewrite or paraphrase article content. The excerpt above is the source publication's own words, sanitized for display. For the full piece — including any quotes, charts, or images — read it at Hacker News. Xela's rewritten version is off for this story, so there's no editorial angle attached — you're getting the source's reporting unfiltered. When the rewrite is on, we add a What this means block underneath with the operator/trader takeaway.

What people are saying

Discussion

Hot takes

0/280

Loading takes…

Comments

Discussion · 0

Sign in to comment, like, and save articles.

Sign in

Loading comments…

Newsletter

Track saas & software every morning.

Daily digest tuned to this beat. The 5 stories most worth your time. Unsubscribe anytime.