SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2412.16620 · 2024

A Large-scale Empirical Study on Fine-tuning Large Language Models for Unit Testing

arXiv · PDF · Open in the Atlas

Code that ran

5 of 5 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 4 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2412.16620.json · badge: /api/ran/2412.16620.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
iSEngLab/LLM4UT_Empirical canonical (classifier label)
classifier basis: classifier_2025
5 ran · 0 no recorded run
FunctionStatusWhere it lives
generate_one Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
iSEngLab/LLM4UT_Empirical/Inference_Script/open_source.py
pointer only (licence: NONE) · get_code("456070524f8a6af5")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, iSEngLab/LLM4UT_Empirical when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

get_prompt_target Ran
ran; our contract draft was wrong, not the code
iSEngLab/LLM4UT_Empirical/Finetune_Script/decoder_ag_main.py
pointer only (licence: NONE) · get_code("38d4c9dc25380d39")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, iSEngLab/LLM4UT_Empirical when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

read_jsonl Ran
ran; our contract draft was wrong, not the code
iSEngLab/LLM4UT_Empirical/Inference_Script/open_source.py
pointer only (licence: NONE) · get_code("02171abe8492fcfd")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, iSEngLab/LLM4UT_Empirical when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

smooth Ran
ran, violated the contract we drafted
iSEngLab/LLM4UT_Empirical/Finetune_Script/decoder_ag_main.py
pointer only (licence: NONE) · get_code("4bcd5408545e929d")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, iSEngLab/LLM4UT_Empirical when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

tokenize Ran
ran; our contract draft was wrong, not the code
iSEngLab/LLM4UT_Empirical/Finetune_Script/decoder_ag_main.py
pointer only (licence: NONE) · get_code("cadd56f46fae79b8")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, iSEngLab/LLM4UT_Empirical when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

Also present in other papers' code

Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 2 later) and 2 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
smooth 5 other papers
4 dated earlier, 1 later
2403.13786 (2024-03)
Chain-of-Interaction: Enhancing Large Language Models for Psychiatric Behavior Understanding by Dyadic Contexts
2406.15786 (2024-06)
What Matters in Transformers? Not All Attention is Needed
2410.14157 (2024-10)
Beyond Autoregression: Discrete Diffusion for Complex Reasoning and Planning
and 2 more not named here
read_jsonl 4 other papers
1 dated earlier, 3 later
2401.10768 (2024-01)
Knowledge Verification to Nip Hallucination in the Bud
2025.emnlp-main.1337 (2025 (year only))
CopySpec: Accelerating LLMs with Speculative Copy-and-Paste
2505.17612 (2025-05)
Distilling LLM Agent into Small Models with Retrieval and Code Tools
and 1 more not named here
tokenize 1 other paper
1 dated earlier
2312.15698 (2023-12)
RepairLLaMA: Efficient Representations and Fine-Tuned Adapters for Program Repair

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Unit testing plays a pivotal role in software development, improving software quality and reliability. However, generating effective test cases manually is time-consuming, prompting interest in unit testing research. Recently, Large Language Models (LLMs) have shown potential in various unit testing tasks, including test generation, assertion generation, and test evolution, but existing studies are limited in scope and lack a systematic evaluation of the effectiveness of LLMs. To bridge this gap, we present a large-scale empirical study on fine-tuning LLMs for unit testing. Our study involves three unit testing tasks, five benchmarks, eight evaluation metrics, and 37 popular LLMs across various architectures and sizes, consuming over 3,000 NVIDIA A100 GPU hours. We focus on three key research questions: (1) the performance of LLMs compared to state-of-the-art methods, (2) the impact of different factors on LLM performance, and (3) the effectiveness of fine-tuning versus prompt engineering. Our findings reveal that LLMs outperform existing state-of-the-art approaches on all three unit testing tasks across nearly all metrics, highlighting the potential of fine-tuning LLMs in unit testing tasks. Furthermore, large-scale, decoder-only models achieve the best results across tasks, while encoder-decoder models perform better under the same parameter scale. Additionally, the comparison of the performance between fine-tuning and prompt engineering approaches reveals the considerable potential capability of the prompt engineering approach in unit testing tasks. We then discuss the concerned issues on the test generation task, including data leakage issues, bug detection capabilities, and metrics comparisons. Finally, we further pinpoint carious practical guidelines for LLM-based approaches to unit testing tasks in the near future.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2412.16620")
get_code_for_paper("2412.16620")
have("2412.16620")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2412.16620.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2412.16620.svg)](https://syntology.ai/paper/2412.16620)

Connect an agent — have() is free.