Repository navigation
test: golden-file compatibility corpus for every file format version #391
Description
Problem
tests/fixtures/ holds one file, compat.graph. tests/migration_matrix_test.rs checks v7 round trips and one empty v3 file. No committed file with real data exists for v1, v2, v4, v5 or v6, and there are no v7 files that match real-world use:
- files written by several checkpoints
- files after a crash-triggered index rebuild
- files with multi-valued facts
v3.0.0 will drop v1–v6 and add a v7→v8 migration. It is a one-way change, so v7 files need to be frozen as fixtures before the v8 work goes further.
Ask
- Build a set of golden files, each with a manifest of the expected query results:
- one file per supported format version, with real data;
- v7 files written by several checkpoints;
- a v7 file whose indexes were rebuilt on open;
- a v7 file with a leftover WAL;
- a v7 file with same-transaction multi-values (to check that the v8 migration recovers them, bug: same-transaction multi-valued facts read back as ONE value, differing between EAVT and AEVT; a batched retract can leave retracted values visible #371).
- A CI test opens each golden file with the current build and checks the manifest, both before and after migration.
- Rule: every release adds golden files for any new format behavior. Golden files are never regenerated, only added.
Activity
Merge pull request #455 from project-minigraf/test/391-golden-corpus
Merge pull request #456 from project-minigraf/test/391-golden-v8
adityamukho commentedon Oct 6, 2026
Done on
v3in #456. The v7 corpus landed onmainin #455. There are 13 golden files: six v7 files from minigraf 2.0.3, checked after migration, and seven v8 files frozen at23aa57c. Each has a manifest. Golden files are add-only, and thegolden-corpusjob inpolicy.ymlenforces that.release: v2.0.4