Evidence quality

A screenshot is evidence only when it answers a question

A screenshot can show a displayed value, message, or state. It usually cannot establish everything about the transaction that produced it. When a test concerns an interface, a screenshot of a green status may omit the source identity, transformation, receiving record, and retry behavior.

Author
Byline approval pending
Published
Not yet published
Last technical review
Pending
Category
Evidence quality
Reading time
6 min
Status
Editorial preview
01Intended use02Credible failure03Proportionate evidence04Defensible decision
A decision-focused assurance chain: every transition requires proportionate evidence.

A screenshot can show a displayed value, message, or state. It usually cannot establish everything about the transaction that produced it. When a test concerns an interface, a screenshot of a green status may omit the source identity, transformation, receiving record, and retry behavior.

Start with the claim

Fictional example. The claim is that ERP prevents issue of quarantined material received through a warehouse interface. Useful evidence needs to connect the source disposition, transferred transaction, accepted ERP state, and attempted issue.

A screenshot of the blocked issue can help. A message log and transaction identity can establish the connection. A reviewed expected mapping explains why quarantine is the correct input. Together, they support a stronger conclusion than a large folder of disconnected screen captures.

Three situations

For a visual defect, a screenshot may be central because appearance is the behavior being checked. For a calculation, an independently checked expected result and recorded actual output are more important than an image of the spreadsheet. For a migration, structured comparisons may reveal missing relationships that screen captures cannot efficiently cover.

Keep enough context

Evidence should be associated with the assessed configuration, conditions, execution, result, and relevant exceptions. Protect its integrity and make its location clear. Avoid retaining sensitive information unnecessarily when a controlled test dataset can establish the behavior.

Avoid two extremes

Capturing every click can create review burden without strengthening the claim. Capturing almost nothing can make the conclusion impossible to assess. Choose the representation that helps another qualified person understand what happened.

A practical editing test

For each item of evidence, ask: “What does this establish, and what does it not establish?” If several images repeat the same fact, combine them where the record process permits. If a critical connection remains unsupported, add the missing evidence.

The evidence package should tell a coherent story about the tested behavior. Its usefulness comes from the connection between claim, conditions, observation, and conclusion.