Skip to content
#software testing Dataset Open access

Artifact for "Memorised, Not Generated: Verbatim Recall of Published Fixtures in LLM-Generated Test Data, Measured Across Five Models and Eight Public Schemas"

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)
Software Testing and Debugging Techniques

Abstract

Complete artifact for the empirical study "Memorised, Not Generated: Verbatim Recall of Published Fixtures in LLM-Generated Test Data, Measured Across Five Models and Eight Public Schemas" (submitted to Empirical Software Engineering). Version 1.2.1 adds experiment E1c: the copy-rate measurement (exact-text match, near-match at Indel ratio 0.9, and column-wise overlap against the published human fixture) extended to five models (Claude Sonnet 4.6, Claude Sonnet 5.5, GPT-4o, GPT-5.6 Terra, Qwen3-235B-A22B-Instruct-2507 via OpenRouter) and eight public PostgreSQL schemas (Pagila, Chinook, Northwind, employees, Dell DVD Store 2, ClassicModels, Oracle HR, BikeStores), direct-emission arm, one run per cell, with every cell's generated rows and per-call logs (tokens, latency, stop reason, serving host, sampling settings), the three new subjects' PostgreSQL ports and provenance manifest, a check of which edition of the Oracle HR fixture each model reproduces (current v23.3 versus the 2015-2019 v19.2 edition), and a model-identity check recording, for every model identifier named in the paper, the provider's listing entry and the identifier echoed back by a live call. It retains the v1.1.0 content: (E1) direct emission vs plan-then-execute (SynthData 1.2.2) vs no-LLM vs Faker vs human fixtures on five schemas, two providers, two runs, scored by row-by-row insertion into PostgreSQL 16 with all constraints on and by column-wise fidelity metrics; (E1b) the same LLM arms on identifier-renamed schemas as a memorisation control; (E2, exploratory) the provisioned fixtures injected into the RAITG LLM test-generation pipeline (172 requirements, 4 services, 293 frozen mutants) in three arms plus the pre-registered E2c state-contract arm. Contains the pre-registered plan, frozen inputs with checksums, all scores and metric files, the scoring harness, the analysis scripts (stats_paper.py and copy_rate_stats_e1c.py print every statistic with the label used in NUMBER_TRACE.md), the manuscript source, and an MD5 manifest of every file. External inputs (the eight human fixture datasets, SynthData 1.2.2 on npm, the RAITG harness at 10.5281/zenodo.20285103) are referenced with pinned versions and checksums rather than redistributed.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

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