Rows the driver created and must delete; teardown sweeps these best-effort.
Driver-specific fixture payload (discovered users, created query/category IDs, …).
OptionalPinnedPublished rubric versions captured when the suite started, keyed by rubric id. A version published after the suite starts does not replace these.
The MJTestSuiteRunEntity.ID this fixture set belongs to.
Per-suite-run fixture state established by a driver's
SetupSuiteand torn down (guaranteed, via afinallyinTestEngine.RunSuite) byTeardownSuite. Threaded into everyExecutecall of that suite run viaDriverExecutionContext.fixtures.Keyed by
SuiteRunIDso the per-TypeIDcached driver instance cannot leak one suite run's fixtures into another. Driver-specific payload lives underData; rows the driver created and must delete are recorded inCreatedRecordsso a best-effort teardown can sweep them.Suite hooks only fire for
mj test suite(a suite run exists); they do NOT fire for the standalonemj test runpath, which has no suite — so fixture-dependent tests must be run via a suite.