Test isolation checks
The idea
Each database test file gets its own database, cloned from a template keyed by schema hash. A socket to anything but loopback fails the test, CLIs are fakes, and deploy gates run in a sandbox.
- The problem
- Tests could touch the network, real CLIs, a person's home folder or each other's data.
- Why it matters
- Gates are fast, isolated and repeatable, and they cannot leak or depend on outside services.
- Where it stands
- In production as of
A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.