pr4.7
This commit is contained in:
@@ -1,51 +1,3 @@
|
||||
# PR-4.7 — Verifier Golden Test Suite
|
||||
|
||||
### Briefing
|
||||
|
||||
We need a stable suite of valid and invalid bytecode samples to ensure verifier correctness over time.
|
||||
|
||||
### Target
|
||||
|
||||
* Introduce golden tests for the verifier.
|
||||
|
||||
### Work items
|
||||
|
||||
* Add a set of small bytecode samples:
|
||||
|
||||
* Valid programs.
|
||||
* Invalid programs for each verifier error.
|
||||
* Implement golden tests asserting:
|
||||
|
||||
* Successful verification.
|
||||
* Specific error kinds for invalid programs.
|
||||
|
||||
### Acceptance checklist
|
||||
|
||||
* [ ] Golden tests exist for all verifier error categories.
|
||||
* [ ] Tests are deterministic.
|
||||
* [ ] `cargo test` passes.
|
||||
|
||||
### Tests
|
||||
|
||||
* New golden tests only.
|
||||
|
||||
### Junie instructions
|
||||
|
||||
**You MAY:**
|
||||
|
||||
* Add deterministic golden tests.
|
||||
|
||||
**You MUST NOT:**
|
||||
|
||||
* Modify verifier logic to fit tests without understanding the cause.
|
||||
* Introduce random or timing-based tests.
|
||||
|
||||
**If unclear:**
|
||||
|
||||
* Ask before changing test expectations.
|
||||
|
||||
---
|
||||
|
||||
# PR-5.1 — Define Canonical Syscall Metadata Table
|
||||
|
||||
### Briefing
|
||||
|
||||
Reference in New Issue
Block a user