@xyo-network/xl1-statement-graph-testing
v0.5.3
Published
Dev-only test support for the XYO Statement Graph — fakes, fault injection, lifecycle acceptance, and vocabulary-neutral scenario program execution.
Keywords
Readme
@xyo-network/xl1-statement-graph-testing
Dev-only test support for the XYO Statement Graph:
MemoryStatementDataLake— content-addressed in-memory body store with fault injection (omit= availability failure,corrupt= integrity failure the scan's hash recompute must catch). Ends the per-repoSharedDatalakecopy-paste.FakeStatementChain/FakeStatementBroadcaster— deterministic finalized chain speaking the SDK's structural viewer interface, with independent elevation scripts and same-block payload carriers plus missing-block, truncated-bulk-range, and head-regression fault injection. Tests can omit or corrupt a carrier without changing the transaction commitment;leadingPayloadsis an adversarial D7 ordering fixture that shifts full-arraytxIndex, not a model of the real runner's normal payload order.runClaimAcceptanceScenario— the multi-substrate acceptance scenario (subject claim → redundant claim → multi-hash fan-out → independent second source, with two-clock assertions); the substrate is a parameter, so the same scenario runs against these fakes in unit/browser suites and against a real dev chain unchanged.runScenarioProgram— a vocabulary-neutral symbolic-actor program runner. Consumers supply their own action/check DSL and substrate adapter; the runner owns actor/result bindings, ordered execution, settlement, mismatch collection, and reader invalidation after writes.
License
LGPL-3.0-only © XY Labs / XYO Foundation
