← Guides RESTAURANT

Acceptance Tests for a Simphony–Reservation Integration

Validate Simphony reservation-to-check mapping, duplicate events, cancellation and eligible prepayment scenarios.

SIMPHONY CLOUD · PRACTICAL GUIDE · Rezervem

Editorial concept illustration about Simphony acceptance

Define the acceptance criteria before a demo

Opening a POS check on screen is not sufficient to approve go-live. The reservation, table, outlet, revenue centre, check closing state and payment mapping must be demonstrably correct, including what happens when a step fails.

Happy-path reservation test

Create a test reservation, assign an eligible table and check in. Confirm a check is created only in the intended revenue centre. Record the check reference and corresponding reservation.

Add a test item and close the check at the POS. Verify that supported confirmed spend reaches the correct reservation. Oracle's Checks API operates in the relevant RVC context.

Duplicate and exception cases

Test a reservation without a mapped table, a repeated check-in, a reversed check-in with an empty check and a reversed check-in containing real items or payment. An incorrect action must not silently remove financial records.

Eligible prepayment behaviour

Check the configured tender and remaining balance for a collected prepayment. Test partial, full and over-balance scenarios separately. Distinguish a card authorisation from an actual collected payment.

Reconcile reservation payment records, POS tender records and the payment provider independently.

Document and sign off the acceptance tests

For each scenario record the expected outcome, actual result, date, outlet and approving team. Use controlled test identifiers rather than copying unnecessary live guest information into the acceptance report.

For example, when the same check-in request is sent twice, a generic 'pass' does not show that duplicate checks were prevented. Capture whether the repeated request was linked to the existing check or safely rejected. Do not extend the rollout to another revenue centre until the agreed acceptance criteria are met.

Notifications and recovery

Oracle's STS Gen2 notification reference states that notification delivery has no retry guarantee. Define how a missed status change is detected and reconciled by the integration team.

Complete a pilot outlet before expanding and use the go-live checklist for staff readiness.