Short answer: test realtime participant moderation in a shared stock trading watchlist as an ordered, replayable event trace, and assert state only after an explicit sequence barrier rather than after a sleep. Use that deterministic model for most correctness checks, then keep a smaller live transport suite for subscription, reconnection, and fan-out boundaries.
This is an architecture decision, not a testing trick. A moderator suspending participant p-17 while watchlist edits are in flight creates a question about authority and order: which accepted event is the boundary after which that participant may no longer add a symbol? A timer cannot answer it. The system needs a committed ordering point, an idempotency rule, and an audit record that lets a failed assertion identify exactly what each observer had applied.
No stopwatch required.
How should realtime participant moderation tests keep a stock trading watchlist deterministic?
Separate delivery from meaning.…