A proposed patch is something to review. A successful test is evidence about the behavior that test exercised. A useful record connects the two without claiming more than either establishes.
Keep the identity attached
Start with the repository and revision. Record which files changed and which version of the proposed patch the test used. If the branch moves or a reviewer edits the change, an earlier result should remain attached to the revision that actually ran.
A result without that identity can be easy to misread. The presence of a passing record somewhere in the repository is not evidence that the patch currently under review was the patch tested.
Describe what ran
- The original behavior or payload under evaluation.
- The environment, dependencies and configuration needed to exercise it.
- The outcome on the starting revision and on the proposed change.
- Any selected variants and regression checks that also ran.
- Checks that failed to start, timed out or remained unavailable.
An unavailable environment is an incomplete test, not a passing result. A missing dependency or failed installation should remain visible rather than disappearing into an overall completion label.
Keep the conclusion bounded
A replay can support a statement about the tested path, payloads and environment. It does not establish that every possible attack is blocked, that unrelated findings are resolved, or that the change has reached production.
Keep approval, merging and deployment distinct from verification. A team may choose to require a passing replay before review, but the review and release decisions still need their own records.
Make the record useful to another person
Ask a reviewer who did not run the test to inspect the record. They should be able to find the changed revision, understand the test boundary, see what remained incomplete and locate the evidence behind the stated outcome.
That is the practical test of an evidence record: it helps a second person assess a decision. A decorative success badge cannot do that work on its own.
