From 14b4b7466b22e84ea861bc2b9b15558b8a1f10f0 Mon Sep 17 00:00:00 2001 From: Bruno Baumgartner Date: Thu, 7 May 2026 19:25:19 +0200 Subject: [PATCH] docs: add negative test vectors v0.9 --- docs/NEGATIVE_TEST_VECTORS_v0.9.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/NEGATIVE_TEST_VECTORS_v0.9.md diff --git a/docs/NEGATIVE_TEST_VECTORS_v0.9.md b/docs/NEGATIVE_TEST_VECTORS_v0.9.md new file mode 100644 index 0000000..deddb63 --- /dev/null +++ b/docs/NEGATIVE_TEST_VECTORS_v0.9.md @@ -0,0 +1,28 @@ +## Summary + +This PR adds `docs/NEGATIVE_TEST_VECTORS_v0.9.md`. + +The new public review draft defines intentional FAIL and ERROR test vectors for DigiEmu Core verification. + +It includes: + +- tampered snapshot FAIL cases +- malformed JSON ERROR case +- missing snapshot ERROR case +- missing expected hash ERROR case +- unsupported hash algorithm ERROR case +- unsupported canonicalization ERROR case +- invalid field type case +- expected reason codes +- conformance relevance + +## Why this matters + +DigiEmu Core should not only verify valid snapshots. + +Implementations must also correctly distinguish: + +```text +PASS = computed hash matches expected hash +FAIL = processable input with mismatched hash +ERROR = verification could not be completed \ No newline at end of file