ms2k/lazaret
SHA256
Watch
0
Code Releases 3 Activity

Confine verification tooling to current repository checks

Browse source
This commit is contained in:
ms2k 2026-07-14 02:17:49 +09:00
commit c738d92f01
1 changed files with 798 additions and 2926 deletions
Download patch file Download diff file Expand all files Collapse all files

7
tests/fixtures/README.md vendored
View file

@ -1,7 +0,0 @@
# Fixture conventions
Fixtures are immutable inputs grouped by the verifier that owns their format. Use descriptive lowercase directory names and commit expected outputs beside inputs when exact bytes matter. A fixture directory must contain a `fixture.toml` with `schema`, `case`, and `expected` fields; paths in that file are relative to its directory.
Positive and negative cases remain separate. Negative cases name the rejected condition and assert the stable error category, not incidental wording. Physical and failure fixtures also record the verification level, durable checkpoint, and exact identity fields under test. Generated, downloaded, host-specific, credential-bearing, and mutable runtime data are not fixtures.
Tests must copy writable inputs to a test-owned temporary directory and remove it on success or failure. Retained corpus updates are reviewed as input changes; tests never rewrite committed expected output.