goldenscript's data-driven golden master approach is compelling for compiler and VM testing. One ergonomic gap I noticed: updating golden masters currently requires manual file replacement after reviewing diffs.
A CLI subcommand like goldenscript update <test-path> that:
- Re-runs the test
- Compares actual output against the stored golden master
- Shows the diff and prompts (or accepts
--yes) to overwrite
This mirrors the insta review workflow and would make it faster to bulk-accept expected output changes during development. The prompting could support --accept-all for automated use in scripts.
Happy to draft a more detailed spec if this aligns with the project direction.
goldenscript's data-driven golden master approach is compelling for compiler and VM testing. One ergonomic gap I noticed: updating golden masters currently requires manual file replacement after reviewing diffs.
A CLI subcommand like
goldenscript update <test-path>that:--yes) to overwriteThis mirrors the
insta reviewworkflow and would make it faster to bulk-accept expected output changes during development. The prompting could support--accept-allfor automated use in scripts.Happy to draft a more detailed spec if this aligns with the project direction.