Make verification reproducible and honest

First, build a mental model

Verification is an evidence record: exact input, candidate, environment, command and observed outcome. A status word without that record is only a claim.

1. Inject clocks, random seeds and external results where practical. Deterministic fixtures make a failed expectation explainable rather than intermittent.
2. Isolate storage and cleanup by test. Tests that depend on execution order can pass in one run and fail in another.
3. Record the tested revision and actual command/exit status. A skipped or blocked subcheck must remain skipped or blocked, even if an outer script exits zero.
4. Visual results also depend on browser, platform, fonts and viewport. Changing a baseline is a reviewed product decision, not an automatic way to make a test green.

function isExpired(expiresAt, now) {
  return now >= expiresAt;
}
const fixtureNow = 1000;
console.log(isExpired(1000, fixtureNow)); // true
console.log(isExpired(1001, fixtureNow)); // false
// No wall clock is needed to test the boundary.

1. Controlled input

   The test chooses the instant rather than waiting for real time to pass.

2. Boundary

   Exactly at expiry is expired; one unit before expiry is not.

3. Reproducibility

   The same inputs give the same answers on the next run.