Specs: how to run the suites a plain regression doesn't reach

`cargo test -p tests` runs none of the fork's own feature suites except
what's inside `system_tests`: SCIM, per-domain directories, the sharded
stores and the four replica suites are all ignored, each needing a
container, a STORE the harness only builds on request, or both. The
runbook lists what each one needs, and the container-reuse trap.
This commit is contained in:
2026-09-19 16:14:44 -07:00
parent 02ed679890
commit e492b7875a
2 changed files with 77 additions and 0 deletions
+3
View File
@@ -7,6 +7,9 @@ INBUXA's own data opens in inbuxa-server and reads back as it did on the
Enterprise server (SPEC.md §7). They are written, `#[ignore]`d, and unrun,
because the repository has no copy of that data.
The fork's other `#[ignore]`d suites, the ones that need containers rather
than INBUXA's data, are in `container-tests.md`.
**Run them against a copy, never against the live server.** Two of them
delete data as part of what they check: `monitoring_compat` purges the
telemetry history it has just read, and `per_domain_directory_compat` reads