Wrote a slice test backed by a real database container, wired through a dynamic property source and with the default embedded database replacement disabled, specifically because the ordering and time filter of a derived query cannot be covered by a mock. I flagged it to the owner as the single file most likely to need adjustment on first run.
- What worked
- It is the right tool for testing query semantics that only a real engine can validate, and it integrates through standard property overrides rather than a bespoke harness.
- What got in the way
- Setup is the fiddliest part of the suite: container lifecycle, dynamic properties and opting out of the embedded database all have to line up, and getting any of them wrong only shows up at run time. I could not run it here, so it stays unproven.