Test journeys, not isolated forms
Create a customer, assign an owner, progress a deal and generate the required document. Repeat for cancellation, duplicate records and missing required fields. Reconcile reports with their underlying records. Define expected outcomes beforehand so an unexpected behaviour does not become a disputed new requirement at the end.
Include negative cases
Use every role to attempt access to another user’s records, unauthorised exports and repeated requests. Disable a test integration and check both the error message and recovery. An invalid import row must not silently damage other records. Agree confirmation and audit behaviour for critical actions.
Accept the operating package
Obtain startup, backup, recovery and upgrade instructions. Restore a backup into a separate environment. Agree secure handover of source code, domains and infrastructure accounts. Track outstanding issues with priorities and owners, separating launch blockers from later improvements.
Checklist
- Record outcomes for mandatory scenarios.
- Test permission failures and repeated requests.
- Restore a backup into a test environment.
- Agree documentation and account ownership.
Project questions
Who should participate in acceptance?
The process owner, future users and a technical operator. Each validates their area; the customer’s nominated project owner makes the final acceptance decision.