aboutsummaryrefslogtreecommitdiffstats
path: root/docs/store.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 14:38:16 +0000
committertv <tv@krebsco.de>2026-11-16 16:26:55 +0100
commitf2ed3e1e9e9c6199fb0bc3b1e2efb4eeb5f89b05 (patch)
tree4ccdd3eb355ec436dd5f9eb32b1fcc32780577bb /docs/store.md
parent0dde043f1e8c6e8c99a876b4d0dffdd499a9c961 (diff)
docs/federation-tests: how the store and the federation are tested
A plan, the contract the code is built to: the fold and the store tested as pure code, events in and verdicts and states out; a model written plainly from the design, which the store is checked against; every rule by its smallest scenarios; every attack row a test named by its table and number, and a test that every row has one; the promises as properties over generated histories, every order for small ones and seeded ones beyond, cut down before they are printed; the store on Automerge checked against the store in memory; simulations with an adversary node; fixed vectors for every encoding; fuzzing and mutants in longer runs. All of it behind the `federation` feature, by stage.
Diffstat (limited to 'docs/store.md')
-rw-r--r--docs/store.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/store.md b/docs/store.md
index c51b9ca..952953c 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -349,7 +349,8 @@ crafted changes. *Sim*: a simulation. *Bench*: measured, not judged.
## Tests
-What the tests check of the store, with a fold made for them:
+What the tests check of the store, with a fold made for them
+([`federation-tests.md`](federation-tests.md) says how they are built):
* **Order.** For every order of a set of events that puts each after its dependencies
(all of them for small sets, seeded ones for larger), the state is the same, and so