Article · Testing

A screenshot is evidence only when it answers a question

How to choose evidence that connects a test claim, the conditions and the observed result.

CSVtoCSA editorial · 2 min read · Published · Summary updated 2026-09-21 · Version 1.1

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.

Practitioner interpretation; apply the sources within their scope and follow your approved procedures. Prepared with AI assistance and editorial responsibility. Original publication and source links are retained; this revision updates the summary and resource navigation.

Relevant regulations and guidance

These sources apply within their stated scope. The suggested worksheet fields, test designs and fictional decisions are practitioner recommendations, unless a source requirement is expressly identified. Completing a template does not establish compliance.

Computer Software Assurance for Production and Quality Management System Software ↗

Regulatory guidance / GMP guideline · United States · February 2026

Scope: Medical-device manufacturers assuring software used in production or their quality management system.

Relevance: For medical-device production or QMS software, supports selecting assurance activities from intended use, risk and available evidence. It is nonbinding guidance and does not determine other sectors’ obligations.

Status: Final / published · Checked 2026-09-21

Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.

Read source details and applicability →

EudraLex Volume 4, Annex 11 — Computerised Systems ↗

Regulatory guidance / GMP guideline · European Union · January 2011 revision

Scope: Computerised systems supporting activities in the applicable EU pharmaceutical GMP context.

Relevance: For computerised systems used in EU GMP activities, informs lifecycle, supplier and record controls. Confirm applicability to the actual activity; the example does not establish it.

Status: Final / published · Checked 2026-09-21

The Commission index confirms the January 2011 operative revision. The linked PDF could not be retrieved in this check; retained detailed section mappings need review against an authorized copy.

Read source details and applicability →

21 CFR Part 11 — Electronic Records; Electronic Signatures ↗

Regulation · United States · Current eCFR text

Scope: Electronic records and signatures within FDA Part 11 scope, tied to the underlying required records.

Relevance: Assess applicability to electronic records required by FDA predicate rules and electronic signatures used in their place. The presence of an electronic record alone is not an applicability conclusion.

Status: Final / published · Checked 2026-09-21

Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.

Read source details and applicability →
Was this useful? Leave feedback

Was this resource useful?

Tell us what helped and what could be clearer. Usefulness feedback does not establish technical validity or regulatory compliance.

Loading contribution options…

Questions and moderated discussion

Questions and discussion

Ask a question or share a perspective. Contributions are reviewed before publication.

Loading contribution options…

Suggest a correction

Sent privately to the editorial moderation queue. Your account email and correction are not published as a comment. Do not include confidential or personal information.

Resource: A screenshot is evidence only when it answers a question

Loading sign-in status…

Correction details