Retest Evidence

Retest Evidence

Retest Evidence

Build a compact retest pack before changing the implementation. Pair each degraded trace with expected state and an output label, then confirm that restart, replay, and pressure preserve the consumer-facing explanation as well as the processor’s internal result.

Build the trace set in a deliberate progression: on-time, late inside policy, late outside policy, duplicate, replayed, and schema-changed events. For restart tests, write the expected state before failure, after checkpoint restore, and after replay. Comparing those states reveals whether recovery preserved the same decision or merely restarted the process.

Assign an expected output label—provisional, revised, stale, diverted, held, or final—to each trace before running it. Add lag and pressure scenarios that expose alert priority, source throttling, and stale-output behavior. The final evidence belongs at the consumer boundary: it must explain why a result changed, why it was withheld, or why it can no longer be treated as current. That record turns a retest into proof of maintained meaning rather than a simple “processor running” check.

Back to the chapter