T01 · Known post
Find one approved source post after the agreed capture window.
Acceptance evidence: Account, content, source reference and timestamp can be matched to the known sample.
1. Prepare the test
Use an authorised demonstration account or approved existing records. Do not publish test content to a public production account without permission.
Name the service/version, evaluation dates, account scope and people who can accept the results.
Record references to approved posts, comments and conversations with known dates and source context. Keep sensitive content out of this pack.
Get a written statement of supported content, capture start, limitations and expected delay.
Mark the must-pass scenarios before the test. An untested critical requirement blocks acceptance.
Run and record the tests
Choose Pass only when the expected result is supported by evidence. Use Not applicable only with a documented scope reason. Record the tester and date with each result.
T02 · Conversation context
Retrieve a known post with comments/replies that are within confirmed scope.
Acceptance evidence: The reviewer can understand the conversation; missing items are explained and logged.
T03 · Search and date boundaries
Search for a known phrase, account and date range; check the timezone and boundary records.
Acceptance evidence: Expected sample records are found; any exclusions have a documented reason.
T04 · Export readability
Export the sample and have another person open it outside the service.
Acceptance evidence: Content, source, dates and context are usable; output reconciles with the selected records.
T05 · Access controls
Using approved test roles, check search, export and administration permissions.
Acceptance evidence: Allowed tasks work and restricted tasks are denied according to your access plan.
T06 · Edits and removals
Only where supported, use approved test content and compare before/after records.
Acceptance evidence: Observed behaviour matches the written scope; do not assume recovery before capture began.
T07 · Connection interruption
Agree a safe demonstration of a connection problem and recovery with the vendor.
Acceptance evidence: The responsible person can identify the interruption, follow recovery steps and assess any gap.
T08 · Exit and handover
Review the exit terms and open a representative export in the intended receiving workflow.
Acceptance evidence: Format, access, effort, timing and any limits are documented; a sample is not proof of a full migration.
2. Resolve gaps
Treat a failed, blocked or untested item as an open question. Do not silently turn it into a pass.
Reference the test ID, expected outcome, observed result and operational impact.
Record who will investigate, what evidence they need and when the result will be reviewed.
Keep the initial result. Record the changed version/date, retest result and evidence reference.
3. Acceptance and handover
The records and IT owners make the decision. A number of passed tests alone is not a compliance assessment.
Choose accept, accept with explicitly approved exceptions, extend evaluation or reject.
State the operational restriction, accountable owner and review date for every accepted exception.
Record ongoing account checks, review responsibility, export storage and escalation contact.
Record approver roles, date, evidence location and next review.
Use the result
Share unresolved test results with the service provider and your internal reviewers. Keep the original evidence and retest history with your decision record.
This is an original planning aid, not legal advice, a retention authority or a certification. Apply your own records, privacy, procurement and security requirements.