How to test a system before accepting delivery
Accepting a system requires verifying that the delivered version supports the agreed processes. A successful presentation helps, but the team also needs to try errors, permissions and recovery. This guide helps prepare an evidence-based assessment with responsibilities and a clear decision about use.
By the end, you can:
- Prepare tests linked to requirements
- Record reproducible problems
- Decide acceptance using evidence
Define what is being accepted and by whom
Identify the version, configuration, integrations and data included in delivery. Link requirements to journeys the team can perform. Separate functions ready for use from those still in development. Without this boundary, a test may assess a different combination of versions from the one that will be used.
Microsoft’s testing guidance connects scope, risk, cases and responsibilities. Name representatives of real roles, including system administration and exception handling. The approver must be able to understand evidence and known limitations even without following implementation details.
| Acceptance element | Fictional example |
|---|---|
| Delivery | Request management, version 1.2 |
| Scope | Reception, assignment, execution and closure |
| Outside this delivery | Purchasing and automatic invoicing |
| Participants | Reception, technician and coordination |
| Evidence | Executed cases, results and identified problems |
Prepare an environment for testing without affecting customers
Use a separate environment with representative configuration and fictional data or data prepared for this purpose. Identify differences from production: volume, integrations, permissions and equipment. If a difference prevents verification of a requirement, record it as a test limitation rather than considering the test complete.
Control emails, messages, payments and other external actions. Use suppliers’ test environments where available and confirm no automation communicates with real contacts. Reception, technician and administration accounts must be separate so tests do not benefit from permissions above normal use.
Prepare equipment used in operations: phone, barcode reader, printer or any other necessary resource. A journey working on the demonstration computer may reveal difficulties on the device the team actually uses.
Write cases with expected results before execution
A test case includes initial condition, steps, data and expected result. Link it to the corresponding requirement. Ask a user to execute the steps without constant assistance from the system’s builders. If instructions are ambiguous, improve them; if the system requires undocumented knowledge, that is useful adoption feedback.
Microsoft recommends scenarios resembling a working day for user acceptance. In the fictional example, reception creates a request, coordination assigns it and the technician records the intervention. Checks also follow what each person can see after handover to the next stage.
Requirement: R-12 — transfer by coordination
Precondition: request P-101 open, assigned to technician A
Account: coordination in the test organisation
Steps: open P-101; choose technician B; give a reason; confirm
Expected: B becomes responsible; the change appears in history;
A’s access follows the new assignment.
Check: consult using the accounts of A and B.
Observed result: complete during the test.
Evidence and linked problem: complete during the test.Include errors, limits and prohibited operations
After the normal journey, introduce situations occurring in operations: missing fields, an unsuitable file, repeated submission, lost connection or simultaneous change. Confirm the message explains the possible action and that already valid work does not disappear without warning.
Test limits defined in requirements: session capacity, available quantity, a status no longer allowing editing or an unauthorised role. These tests should verify the system result, rather than just a button’s appearance. Access checks must cover searches, attachments, exports and direct record links.
| Situation | Acceptance question |
|---|---|
| Required field absent | Can the person identify and correct the problem? |
| Same request submitted again | Does behaviour prevent improper duplication? |
| Two users edit | Is conflict handled according to the agreed rule? |
| User outside scope | Are the operation and data protected? |
| External service unavailable | Is there a clear status and a recovery option? |
Check performance, data and continuity
Functional tests do not replace checks of imported data, accessibility, performance and recovery. Choose critical operations and representative conditions: record count, filters, device and connection. Compare with agreed objectives. A measured time without these conditions is difficult to interpret or reproduce.
Open a sample of migrated records and check relationships, dates and attachments. Run a recovery test proportionate to the system with technical support. Also confirm documentation, training and the support channel. The team should know how to report a problem and continue permitted work while awaiting resolution.
These exercises complement implementation’s technical tests. Business acceptance demonstrates suitability for the journeys assessed; it does not replace a specialist security assessment where scope requires one, or demonstrate the absence of every possible defect.
Record reproducible problems and verify corrections
For each problem, state the version, test account, data, steps, expected result and actual result. Add evidence without exposing unnecessary data. Distinguish defects, configuration issues, usability difficulties and improvement requests. This lets resolution be assigned correctly and scope changes discussed clearly.
Classify by impact: blocking an essential journey, compromising data or access, hindering a task with an alternative, or improving presentation. Avoid deciding by problem count alone. One customer-isolation error may matter more than several visual differences.
After correction, repeat the case and affected journeys. Record the version containing the fix and evidence of the new result. A message saying “it is fixed” does not close the test. If the correction changes a rule, also review the requirement and associated examples.
Accept a specific version with explicit conditions
Bring together results, open problems and environment limitations. Decide to proceed, proceed only within a defined scope or postpone, according to agreed criteria. Issues affecting data, access or the essential journey need handling before an approval incompatible with the identified risk.
For accepted outstanding issues, name an owner, temporary workaround and resolution condition. Separate acceptance from post-launch follow-up: the first days still need support and observation. Keep the worksheet with the version and date so everyone knows exactly what was assessed.
Worksheet for your project
System acceptance worksheet Version, configuration and environment assessed: Included scope and features outside delivery: Requirements and linked test cases: Participants, roles and test data: Normal journeys, errors and permissions checked: Migration, performance and recovery checks: Results, evidence and reproducible problems: Corrections, versions and retests performed: Test limitations and outstanding checks: Agreed acceptance criteria: Decision and conditions of use: Accepted outstanding issues, owners and agreed deadlines: Documentation, training and launch support: Approver and date:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
