Turn requirements into checks
For each requirement, define an action and an observable result. “Working form” may include entry, validation, storage, notification and confirmation; check every included step. Use identifiable test data and do not send real information to unknown recipients. Record outcomes, dates and evidence sufficient to repeat the check.
Check different conditions
Repeat tasks on mobile, with a keyboard and in included languages. Try long text, empty fields and invalid data. Check that errors and waiting states have clear messages. A visual homepage review does not establish that navigation, editing, search or integrations work.
Rehearse failures and recovery
In a test environment, simulate an unavailable source or rejected response. Check that the interface does not report false success. Review who receives the issue and how the task resumes. For critical functions, agree an appropriate recovery test before relying on them in production.
Finish with a controlled handover
Receive documentation, access and an owned list of remaining items. Separate defects in agreed scope from new requests. Confirm backup location and support arrangements. Acceptance should describe what was actually checked and identify limitations that still remain.
Key takeaways
- Acceptance needs evidence of behaviour, not just screenshots.