Files
mesh-delivery/modules/mesh-delivery-checker/internal/check/testdata/captured/README
T

10 lines
975 B
Plaintext

go-test-failing.json, go-test-slow.json, go-test-empty.json and go-digest.json are what mesh-catalog's mesh-build-go answers
(TestResult and DigestResult, cmd/mesh-build-go levels.go and digest.go), marshalled by the module's own code: a throwaway
test beside the module's test_test.go and digest_test.go (workspaceFor + runUnit on the fixtures testdata/captured/failing,
slow and empty, and digestFixture + digests on testdata/repos/digest) at mesh-catalog origin/main cdbdb474, captured on
2026-10-21 for issue 1679 and not kept there. The fixtures' package names are the build module's own (fixture/failing/bad...).
The fields a fetch with a base adds (base, merge, conflicts, changed, trees) are the contract the lead relayed to the
mesh-catalog agent (ADR 0484 clause 3, 2026-10-21); mesh-catalog's fetch step is not on main yet, so the fetch fixtures in
the tests are written from that contract and are to be replaced by a capture once its fetch_test can marshal one.